Stavros Macrakis wrote:
>
> For one thing, unlike other cygwin programs (e.g. bash), it doesn't
> seem to
> understand Windows-like file syntax, e.g. load("c:/temp/foo.lisp"); it
> prefers load("/root/temp/x.lisp"). This means that any code/scripts
> involving filenames needs to be parameterized. It would be easier if it
> simply understood the c: syntax, like other cygwin programs. Also, it
> doesn't like spaces in filenames, and I couldn't guess what the
> convention
> is for representing them.
Sometimes people specify short name like C:\PROGRA~1\
(I don't like this approach very much)
sometimes it is sufficient to escape space with "\" char
But more general approach - is to avoid blank spaces, for example using
symlinks or such.
> I suppose these are a clisp problems; can we get
> them to fix them?
I agree.
Interestingly, clisp/win32 accpets pathnames like d:/filepath
clisp/cygwin rejects such names...
I am sure this should be asked on CLISP mailing list.
I'll go and ask :)
>
> Now I am trying to get it to find wgnuplot, which Windows Maxima
> installs in
> c:/Program Files/Maxima-5.11.0/bin/wgnuplot.exe. Since there is a
> space in
> that filename, I copied wgnuplot to c:/temp/wgnuplot.exe and set
> gnuplot_command: "/root/temp/wgnuplot.exe". But now plot2d(sin,[x,0,1])
> gives "Syntax error: "&" unexpected". In case the wgnuplot
> installation is
> path-dependent, I also tried doing this with a link from c:/gnuplot to
> c:/Program Files/Maxima-5.11.0/bin/ -- which also gave "& unexpected".
I believe that & sign is misinterpretation of "background" execution of
program;
My guess that it is clisp's problem;
>
> What is the correct way to have clisp know about the existing wgnuplot?
> Also, is there any way to handle this so I don't have to update the
> wgnuplot
> path every time I move to a new version of Maxima?
I suppose it is enough to treat it as already in PATH.
Best regards,
Vadim.