|
| From: | Abhinav Tripathi |
| Subject: | Re: Windows: different behaviour of octave.bat and octave-cli/gui.exe regarding modifying path |
| Date: | Tue, 9 Aug 2016 12:40:58 +0530 |
On Aug 9, 2016 1:38 AM, "Nicholas Jankowski" <address@hidden> wrote:
>
>
> 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.
Hi Nicholas,
Thanks for the explanation.
How about having the path such that it gives higher precedence to octave files over windows?
I mean currently, if I open octave (by the exe files), the PATH is atleast "<windows-path>;<some-octave-dirs>;" how about swapping the 2 parts such that the octave dirs are prepended and not appended?
Even that would help resolve issues while installing packages...
.
Abhinav
| [Prev in Thread] | Current Thread | [Next in Thread] |