[Octave-bug-tracker] [bug #41924] build_packages - probelms with path

[Philip Nienhuis]

Follow-up Comment #1, bug #41924 (project octave):

> - Octave should make sure that it only uses the tools (like sh)
> from its binary directory and not from what it finds in the
> search path.

IMO it would be better to either:
- Prepend, rather then append, <OCTAVE_HOME>/bin to Windows' PATH while
starting Octave; 
...or if this is not possible,
- Start Octave from a batch file along the lines of:

@echo off
set PATH=<OCTAVE_HOME>/bin;%PATH%
start octave
exit

Even better if %PATH% here could contain only the essential Windows
subdirectories plus <Ghostscript>/bin (in a path w/o spaces).
This way all kind of interfering junk can be weeded out of the PATH before
that is inherited by Octave's process slot.


> - Octave should be able to handle spaces, parentheses, Umlauts
> etc. as one would expect today in the 21st centrury where some
> people are already beyond the ASCII character set. For example
> the GUI prototype does not show Umlaits and special characters
> properly.

This has been brought up a number of times; AFAIU we need a complete Unicode
build chain and maybe an overhaul in some dependencies.
As Octave is a *nix program, running it on Windows gives the union of the
limitations of both OSes.
So while you're right here (IMO) it isn't something that is to be expected
soon.


    _______________________________________________________

Reply to this item at:

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

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