Hello *,
> I use the workarround (root)
> mkdir /libexec
> ln -s /usr/local/libexec /libexec
> since omplotdata is in /usr/local/libexec/maxima/5.9.0rc3/
> in my mandrake 8.2 box.
As a workaround, this is OK, but this does not solve the problem.
> > What function[s] in maxima construct this directory name,
> > and why they get confused by the TeXmacs interface?
> >
>
> Sorry, I don't know, and there are many more important
> issues with TeXmacs for the moment, so I don't ask for Joris'help.
> (Also maxima's help does'nt work from within TeXmacs).
TeXmacs itself has nothing to do with the problem (so, Joris cannot help
even if he would like to). texmacs.lisp redefines a few Maxima functions
(prompts, LaTeX generation). This *must not* change the behaviour of any
other parts of Maxima, in particular, the logic of paths construction. But
it does. So, this is a bug either in Maxima, or in texmacs.lisp. I want to
trace the functions which construct the string with the path to
omplotdata. I have to know if they call any function redefined in
texmacs.lisp (very unlikely), and at which stage of constructing this
string things start to differ.
So, the question to Maxima gurus: Which functions construct the string
with the path to omplotdata?
Andrey