Georg Baum wrote:
Steve Harris wrote:
I'm not sure that asking if you have a full Python installed is
relevant.
That was only a shot in the dark, because we have had problems with stripped
down python versions in the past.
SH: In that sense it does appear to be relevant. Rescan will work if
there is a system Python in Windows Path and the LyX Python package
is deleted. The LyX Python package does not cause Rescan to work if
the system Python is the same version, or not the same version, in
the Path or not. Nor if the system Python is uninstalled.
The LyX Python package apparently does have a working python.exe
since I think the LyX directories are prioritized for executables,
and "python texfiles.py" produces .lst files. Then if those .lst
files are copied from the Script directory wherer they are made to
Resources, then Rescan will produce content in the Tex Info window.
A regeneration process doesn't seem to happen.
Bo Peng and I have confirmed the OP complaint. Two others have
stated that the LyX local python package works, so it appears
to be an environment issue, but it is not the system-wide Python
that produces the conflict since I have tried uninstalling that
first and the Win XP Pro LyX1.4.2 local python package fails.
I will file the above as a bug report.
That is strange. On linux Rescan regenerates the files. Please somebody file
a bug.
Georg
--
Stephen
"Once you eliminate the impossible, whatever remains, no matter
how improbable, must be the truth." SH: Sherlock Holmes (Doyle)
