Hi again, On Wed, Oct 21, 2009 at 12:26 AM, Uwe Stöhr <uwesto...@web.de> wrote: > 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?
As a matter of fact, configure.py does not _find_ the other scripts; it merely writes them to the configuration file lyxrc.defaults, so that LyX can later execute them. As in your version, these scripts are preceded by $$s/scripts, which allows LyX to find them. > Can you please recheck because it must work. I just did that, on Debian and on a Windows machine. On both instances it works as expected: if elyxer.py is in the scripts folder but not in the execution path, then LyX does not find eLyXer. I am sure that you must have some copy of elyxer or elyxer.py lying around from previous tries; it might be in c:\win32, or in the same folder as lyx.exe. Could you check that typing "elyxer.py" in a console does not execute anything? > Why do you then don't agree to include eLyXer to LyX? No matter what I may have said before, I would love eLyXer to be included in LyX. There are some practical problems but nothing that could not probably be solved. >> 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. Only on Windows, I think; and your installer can take care of that. Just consider that on Linux (e.g. Debian) package installation is completely different: each package places a binary in /usr/bin, and they are all supposed to work together without making any copies anywhere. That is why the execution path is so important on Linux. > You also can provide eLyXer as standalone program, no matter that it is > included in LyX. Sure. This would be fine with me. Alex.
