Re: Windows: different behaviour of octave.bat and octave-cli/gui.exe regarding modifying path

[Abhinav Tripathi]

On Aug 9, 2016 1:20 PM, "Mike Miller" <address@hidden> wrote:
>
> This is precisely what the purpose of octave.bat is.
>
> If you run the executable directly, then it's generally assumed that the
> executable is already in PATH, or that PATH is at least configured such
> that the helper programs that Octave will need are already in PATH.
>
> That behavior is marked with a FIXME comment [1]. I think it would be
> ideal (and I think the FIXME comment agrees with me) if the Octave
> executables did *not* modify the PATH environment variable at all.
>
> Silently prepending Octave's bin and libexec directories to PATH would
> be a severe error on most operating systems, I hope that is easy to see.
>
> Configuring the PATH correctly in octave.bat is a compromise for Windows
> users who do not know how to or do not want to configure the global PATH
> to include Octave's bin directory. Which is probably most users. So
> essentially no one should be calling the executables directly. Is that a
> problem in itself?
>
> [1]: http://hg.savannah.gnu.org/hgweb/octave/file/22c2bd440544/libinterp/corefcn/defaults.cc#l266
>
> --
> mike

Thanks for the explanation.
If I see it from a user's point of view, it seems perfectly alright. I'll use octave.bat for opening octave now.
.

Tatsuro wrote:
> Sorry I have informed you that incorrect writing cli mode startup on windows.
>
>From windows console shell, the cli mode
>(path to octave.bat)\octave.bat --no-gui
>(path to octave.bat)\octave.bat --no-gui --no-qt
>
>At first one, you can use qt graphics toolkit 
>At second one, you only fltk graphics toolkit as opengl graphics.
>
>Tatsuro  

Thanks for the commands. I should have tried/searched for the correct way to use octave executable.

Abhinav