TechTonics wrote:
Joost's version of LyX1.4.2 created a subset of Python2.4.3 and installed it in a sub-directory of LyX even though I had system-wide Python2.4.3 installed and in Windows Path.
This is then a bug. Python should only be installed when it isn't already on the system. This bug is not in my installer.
The LyX local subset Python failed to run the script, TeXFiles.py, and as a result "Tex Information" failed to populate. #!/usr/bin/env python -tt # -*- coding: iso-8859-15 -*- Your script edits the ^15 to a 1, and is a workaround for the script to produce content for "Tex Information".
This is a known bug of LyX 1.4.2. The encoding of the python files is now fixed and I used the fixed versions for the installer release.
Your version did not produce the above problem for me. It found system-wide Python243 and inserted it into the LyX Path_prefix, which was another workaround to Joost's Python malfunction, put the system-wide Python ahead of the Joost version created entry for the local python sub-directory which was in the Path_prefix. I had no LyX local Python sub-dir created for me with your version, plus the script was edited so it would work if it had. Everything went well with the net and complete installs, so far. I have a minor nit. The missing lyx icon isn't mentioned in the Readmes. You did mention in your post, "The executable "lyx.exe" has no LyX icon (see LyX's bug #2708),"
Thanks for the hint. But it is listed in the changelog. The readmes don't cover minor problems of LyX, only general ones.
But I think for new users, including a lyx.ico in Resources ...
There should be a "lyx.ico" in LyX's bin directory. The missing icon will hopefully be fixed for the next LyX release.
thanks for your feedback best regards Uwe
