[Octave-bug-tracker] [bug #49718] Octave crashes on print/saveas etc when installed on a directory with parenthesis

[Philip Nienhuis]

Follow-up Comment #28, bug #49718 (project octave):

Some energy provider mechanic didn't show up today :-( up so I could proceed
(there's always a sunny side isn't it).

With Panxto's patch from comment #23 I get this:

>> plot (1:10)
>> print (fullfile (tempdir, "toto.pdf"))
'C:\PROGRA~1\Octave\OCTAVE~1.0_' is not recognized as an internal or external
command,
operable program or batch file.
error: gl2ps_renderer::draw: internal pipe error
>>


and

>> OCTAVE_HOME
ans = C:\PROGRA~1\Octave\OCTAVE~1.0_(\mingw64


... but not really, it is

C:\Program Files\Octave\Octave-6.0.0_(bug45718)


so apparently the parenthesis is still a problem, confirming what I see in
comment #27.

(BTW I always figured that OCTAVE HOME would be the installation subdirectory
but it is mingw64/ inside it, is seems. Apparently it's like that since the
change to MSYS2).

Anyway, I usually install my Octave crossbuilds into
C:\Programs\Octave\Octave-version_date\
and with one of those installations (w/o patch of comment #23) the example in
comment #23 works fine.

My conclusion:
Octave itself works fine if installed in a path with spaces in the subdir
names, but it's still not totally immune to spaces.


    _______________________________________________________

Reply to this item at:

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

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