Alex Fernandez schrieb:
This is not what I understand from the code. It seems to look for
elyxer.py in all execution paths known to Python, not to LyX. On
Windows these include all Windows execution paths (the %PATH%
variable).
It first looks at the paths known by LyX and then at the paths listed in the PATH variable. Python
is independent of this. But as said, eLyXer is no standalone program with its own installer and thus
its path is not known.
Therefore I was forced to use a certain location for the file and have
chosen the directory where we store all other python scripts. So you can see
eLyXer as a plugin and the scripts folder is LyX folder for plugins.
The problem is that it doesn't work as you think it does, at least on
Linux. On my trusty Debian I have just tried removing the elyxer
package, placing elyxer.py in the LyX scripts folder, and LyX is not
able to find it. I would bet that on Windows it will be the same:
remove elyxer.py from the execution path and try to see if LyX
reconfigure can find the copy in the scripts folder.
This works. I never had elyxer.py in another folder. configure.py also finds the other scripts in
the scripts folder, so why shouldn't it find elyxer.py? Can you please recheck because it must work.
Forcing
the users to copy a single file shouldn't be a too hard task.
It would not be too hard -- the first time. Making users copy it back
every time they update LyX (on Mac OS X), or for every LyX
installation, is not so nice for users. Specially when the check can
be done for them in a few lines.
Why do you then don't agree to include eLyXer to LyX?
- install eLyXer in the path,
What do you mean with "path"?
Execution path. The same folder as LyX.exe would be enough, on
Windows. On Linux /usr/bin is fine.
I can move the file location from the scripts folder to the bin folder but this doesn't change
anything. eLyXer still needs to be copied there.
Finally. as I often stated: eLyXer can only work together with LyX and I
will therefore never understand what it cannot just be another python script
in our SVN. When it would be in our SVN, everybody could fix bugs in the
file in case you are not available. It would be part of every new LyX
release and users can report bugs with this script to our bugtracker.
That is not my decision to make. In any case I maintain that eLyXer is
useful as a standalone tool even for people that do not use LyX,
increasing at the same time the usefulness of LyX itself. People who
have been given a LyX document can use a little script to translate
it, instead of having to download the whole LyX package with all its
dependencies.
But you can already use every Python script that is part of LyX as standalone script. Just download
it from here:
http://www.lyx.org/trac/browser/lyx-devel/branches/BRANCH_1_6_X/lib/scripts
or here:
http://www.lyx.org/trac/browser/lyx-devel/trunk/lib/scripts
You also can provide eLyXer as standalone program, no matter that it is
included in LyX.
regards Uwe
