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

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

[Octave-bug-tracker] [bug #60554] is_system_fcn_file doesn short names


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #60554] is_system_fcn_file doesn short names
Date: Sat, 8 May 2021 05:57:36 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36 Edg/90.0.818.51

Update of bug #60554 (project octave):

                 Summary: Octave default paths stored as short names =>
is_system_fcn_file doesn short names

    _______________________________________________________

Follow-up Comment #1:

Octave on Windows isn't using the hard-coded values for the home directory (or
it wouldn't be able to be installed in an arbitrary directory). At least, that
is the case if started with one of the startup scripts.
Instead, it is using the value of the environment variable OCTAVE_HOME.
For Octave 6, the startup scripts convert the installation directory to a
short file name to avoid potential issues with spaces in paths. See e.g. bug
#59923.
If all goes to plan, that will be different for Octave 7.

So, the values you are seeing in your test file are the ones that are
expected.

The "is_system_fcn_file" function should be able to cope with that though.
I thought I remembered reading about a similar issue somewhere. But I can't
find a bug report for it atm.

Re-titling the report to the specific issue.

If you 

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60554>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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