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

[Tatsuro MATSUOKA]

----- Original Message -----
>From: Nicholas Jankowski
>To: Abhinav Tripathi  
>Cc: octave-maintainers <address@hidden>; Mike Miller <address@hidden>
>Date: 2016/8/9, Tue 05:07
>Subject: Re: Windows: different behaviour of octave.bat and octave-cli/gui.exe 
>regarding modifying path
> 
>
>On Mon, Aug 8, 2016 at 3:52 PM, Abhinav Tripathi <address@hidden> wrote:
>
>Hi,
> 
>I have just one question, why aren't the other executables supposed to modify 
>the PATH when it helps resolve this issue?
>>
>>
>>.Abhinav
>
>you don't want multiple files changing the path when starting octave. the 
>windows version is designed to use available widows scripting language to find 
>the local path and set it. this is done with the octave.bat file. after taking 
>care of startup steps, octave.bat calls the appropriate executable.  
>
>Octave.bat runs the following line:
>
>set OCT_HOME=%~dp0
>
>
>to find the current location of octave and then that gets added to the path.  
>This enables the zip-file "installer" for windows, as well as having multiple 
>versions of Octave installed at one time.
>



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