[Top][All Lists]

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

[Octave-bug-tracker] [bug #53124] [MXE Octave] install in path that incl

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #53124] [MXE Octave] install in path that includes spaces
Date: Tue, 24 Mar 2020 18:24:26 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #31, bug #53124 (project octave):

One hitch is that editing function files is not possible - that is, they can't
be saved unless the user has admin privileges or runs Octave with admin
priviliges  (right click on the Octave shortcut, select "run as
administrator", enter admin password and there you go - that is, if and only
if the required "RunAs" service has been installed and is running).
An alternative way to adapt / edit / debug Octave .m function files (and OF
functions shipped with mxe-octave) and run them, would be to explicitly shadow
them in some way, by e.g., putting them in the cwd or in a subdir in the top
of the path. For hidden functions (in private/ subdirs) that isn't so easy.

This makes me less certain if installing Octave in protected places like
"C:\Program Files" is really such a good idea in the first place.
Installing software there is good for programs that aren't supposed to be
changed or adapted by plain users. Are we convinced that Octave and its OF
packages belong to this class of programs?

BTW currently the mxe installers always ask me for admin credentials, no
matter where Octave gets installed - the UAC pops up before the NSIS installer
is even visible. IIRC until some time ago the installer always asked for a
local or global installation.


Reply to this item at:


  Message sent via Savannah

reply via email to

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