Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side. CheckL
Op 7-5-2012 13:55, Vincent van Ravesteijn schreef:
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actual
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side. CheckL
2012/5/7 Vincent van Ravesteijn:
> I think it is not necessary
> to check for luatex every time LyX is started, but just once when we
> reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side. CheckLuateX() is only issued when LyX is
reconfigu
Everytime I start up LyX 2.0.3 a "luatex.exe" process takes quite some
time before LyX appears on the screen.
This is caused by checkLuatex in configure.py. I think it is not
necessary to check for luatex every time LyX is started, but just once
when we reconfigure LyX.
Vincent
