octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #45899] Installing on Windows - initial workin


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #45899] Installing on Windows - initial working directory
Date: Mon, 14 Sep 2015 13:13:00 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0

Follow-up Comment #5, bug #45899 (project octave):

I have never seen this (not even on one of my Windows boxes where I still work
with admin privileges, I still forgot to make myself power user there). But
that I didn't see it may have the following reason:

Reading Lloyd's (the OP) scenario, I suspect it has to do with an initially
lacking C:\Users\<username>\.config\octave subdir where in the file
qt-settings the start directory is set. qt-settings is only made *after*
Octave starts up for the first time, so that may be why Octave starts up for
the very first time in a "rogue" subdirectory.
If this were true, subsequent Octave installations should not portray this
behavior anymore.  A quick check would be to move this .config subdir out of
the way and see what happens when starting Octave.
Even then, I assume Octave's startup dir should initially be determined by the
"Start in" field in the shortcut (in the Start Menu or on the desktop).
Looking at my Octave installation(s) on Windows, this is currently set to
%USERPROFILE%
So, the above test should be executed with an empty "Start in" field in
Octave's shortcut, or maybe using the tart Menu's "run" command.

Looking in the makeinst-script.sh file in mxe-octave I see this field isn't
initialized there, other than implicitly using $INSTDIR  (= Octave's
installation directory)
...and it would be futile for the GUI anyway as the initial working directory
is set by the user in the Preferences|General tab (= in file qt-settings).

I also see no reason why Octave would start in Windows' system32 folder; I
suppose that can only happen if no start directory has been set anywhere and
Windows' program launcher location is substituted (that probably lives in
%WINDIR%\system32). 
I know too little about NSIS to say anything more specific here.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45899>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]