[Octave-bug-tracker] [bug #60554] is_system_fcn_file fails with short file names

[Markus Mützel]

Update of bug #60554 (project octave):

                 Release:                   6.1.0 => 6.2.0                  
                 Summary: is_system_fcn_file doesn short names =>
is_system_fcn_file fails with short file names

    _______________________________________________________

Follow-up Comment #2:

Oops. Must have hit the wrong button. Here is what I wanted to write:

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).
Instead, it is determining its installation path from the command line.
For Octave 6, the startup scripts convert the installation directory to a
short file name (if possible) 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 probably the ones that are
expected.

The "is_system_fcn_file" function should be able to cope with that situation
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 for the specific issue.

If there are other similar issues we could handle them here or open new
dedicated reports.

    _______________________________________________________

Reply to this item at:

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

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