Hi Joost, On Tue, Sep 15, 2009 at 4:54 PM, Joost Verburg <jo...@lyx.org> wrote: > Wouldn't it be better to solve this problem instead? I doubt it's a bug in > the Windows shell.
Wow, a constructive and enlightening comment -- I've come to appreciate what I once took for granted. Apparently there was enough of an explanation in my message to understand what the problem was, but you were the only one to get it. Note that I was not able to reproduce Uwe's issue with spaces in document paths (when we both had Windows XP on our test machines). That is why I think it is a bug in his particular version of XP. > However, I also think it's not a good idea to use the file association in > the registry for .py files. This is because the Windows installers includes > a subset of python, which is what we use to for all scripts included with > LyX. The python.exe of this bundled version is added to the LyX path, so > when you call python.exe you'll automatically get this one. I would > recommend you to also use the included python, because this way users won't > need to install an external version as well. If some files required by your > script are missing in the subset that is distributed with the installers, > they can easily be added. So you also think that it would be better to do as Uwe suggested and run > python elyxer.py ... Unfortunately this means that placing the file elyxer.py in the path is useless. Now it has to reside in some location where python can find it; Uwe's clever solution was to put elyxer.py in the scripts folder and run > python $$s/scripts/elyxer.py ... This should work fine if the Windows installer Uwe is also distributing eLyXer; for manual distribution it is not so good. And it also breaks completely the detection method for eLyXer in configure.py. Finally, it forces all platforms to put elyxer.py in the scripts folder, even those where it makes no sense and placing elyxer.py in the path is much more straightforward. The solution of using a glue script was the only thing that was: - cross-platform (works on all platforms), - comprehensive (solved all issues), - and user-friendly (both placing elyxer.py in the path and installing eLyXer as a library were covered). Do you have any further suggestions? Thanks, Alex.
