Alex Fernandez schrieb:
Sure. It doesn't work because it tries to run eLyXer as a script, and the script is nowhere to be found. On my Debian machine: $ python -tt elyxer python: can't open file 'elyxer': [Errno 2] No such file or directory
I guess the python executable is in the PATH on Linux and the same applies for eLyXer when it was installed as Debian-package.
Changing it to elyxer.py is no good: $ python -tt elyxer.py cBN-Uli.lyx cBN-Uli.html python: can't open file 'elyxer.py': [Errno 2] No such file or directory
This of course also only works when elyxer.py is in the list of LyX's known paths.
If we happen to run it from the same directory where elyxer.py resides, then it works: $ python -tt elyxer.py cBN-Uli.lyx cBN-Uli.html but this is not a practical solution since it will normally be run from the documents directory.
How that? when I install a program a certain location is chosen for the executable. My documents are never in the folder of installed programs (not allowed on Windows when you don't haev admin permissions).
Revision 31950 was good, just adding the removed comment line (for info and consistency with other versions) should be enough. Please find attached the patch.
I must admit that I still don't understand why a python script like elyxer cannot be run by calling Python. But I nevertheless tested your solution again and it works this time at least also for Windows when Python is completely installed. I therefore applied your patch now again. I'll test tomorrow if this solution also works with the stripped-down Python version we use in the Windows installers.
Yesterday the test failed because I used wrong LyX's known paths (that is the negative side effect when you develop an installer that needs many third-party applications :-( ).
So trunk is now OK from your, Pavel's and my side. The same applies for branch. regards Uwe
