Hi,
I saw that if I run octave from '<octave-dir>/bin/octave-cli.exe' or '<octave-dir>/bin/octave-cli.exe' then I only get PATH as "<windows-path>;<octave-dirs>;" which doesn't let me install any packages. I get errors such as 'sort' is not gnu sort or sometimes 'expr.exe' starts crashing (that too repeatedly 10-20 times)...
If I edit PATH (using setenv) such that PATH becomes "<octave-dir>;<windows-path>;" (simply swapping the 2 parts) then I can install packages (using "pkg install").
Also, instead, if I run octave from '<octave-dir>/octave.bat' then it automatically prepends octave's bin dir to PATH and the installation of packages goes smoothly.
Mike said "those executables should not change PATH, what you are seeing is the expected behavior. Setting environment variables like PATH is precisely the point of the bat file."
I have just one question, why aren't the other executables supposed to modify the PATH when it helps resolve this issue?
.
Abhinav