Slash/backslash woes and more mischief
Brought to you by:
joolean
Menu
▾
▴
#14 Slash/backslash woes and more mischief
In the default installation of Octave on Win98 German
Edition no loadpath is defined at all. And I cannot fix
it: Although Octave returns loadpath=c:\tc\ or
loadpath=c:\tc (in case that this web service cannot
cope with backslashes: that´s backslashes) it doesn´t
find any files therein, it doesn´t even tell me that it
hasn´t found a file but says just "no". If loadpath is
in the directory tree of Octave installation, e.g.
"F:\GNU Octave 2.1.36\usr\share\octave\2.1.36", Octave
becomes more informative: "no such file,
'octave_files/\GNU Octave
2.1.36\usr\share\octave\2.1.36/coeffeval.m'.
I can read and write data files without problems, but
script files are just as important. Does Cygwin-Octave
work better under Win2K or an English version of Windows?
It is also strange that one cannot copy, cut and paste
on the command line, neither with ctrl + c/x/v, nor
with a right-click mouse menu, nor with a standard
menu. Is this also the case when running Octave in Unix?
I would propose that you dump the Win32 package. Such
evil bugs creeping out when you have already invested
many hours do miscredit open source software.
Programmers are heros not because they were incredibly
intelligent and fierce but because they bear
responsibility for all of us.
Logged In: YES
user_id=770354
Well, I found out that I can live with the script file read
bug and the lack of paste and copy if I write all commands
into startup\octaverc. Restarting Octave goes fast enough on
my Pentium-II 350Mhz. Furthermore, I would install Unix if I
had to use Octave more frequently and professionally, but
now that I am nearly finished with my project I wish to
thank the programmers and maintainers of Octave.