[Octave-bug-tracker] [bug #50005] MXE Octave: using 8.3 file convention?

[Philip Nienhuis]

Follow-up Comment #3, bug #50005 (project octave):

I was a bit surprised about this as well initially.
Later on, after just working with mxe-octave as it turned out to be, I found
no issues as regards functionality - yet, that is :-)

Admittedly it is a bit of a rough change (but in JohnD's defense: I could have
come up with it myself :-) )

Nonetheless I'd wish I could see the "real" (long) paths that are now mangled
into 8.3 format, but looking at the cset I suppose they're "hard-coded" in the
mxe build and not available anymore.

Of the "special character bugs" mentioned by JohnD here are several
duplicates.

BTW I haven't tried yet but it may well be that one can install Octave now in
paths containing spaces w/o encountering issues.



    _______________________________________________________

Reply to this item at:

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

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