This continues an on-going (and very strange) saga from the user list.
The short recap: someone using LyX 1.4.2 on Windows has a few
MATLAB-generated Postscript image files that do not display correctly in
the LyX GUI. They:
* worked fine with version 1.4.1 (which suggests, not definitively, that
a change in 1.4.2 is related to the problem);
* display correctly if he runs lyx.exe directly;
* display correctly if he comments out either of the two SET commands
in lyx.bat (but do not display if he replaces the commented-out SET
command with a SET of equal total length, implying that the content of
the SET commands is not an issue);
* change behavior if he futzes with the lengths of SET (meaning a
formerly undisplayed image will display, and a formerly displayed image
will not);
* display correctly if he shortens their file names by one character
each (not clear that one character will cover future offending images,
though).
Within the same document are other PS images that always display
correctly. When an image fails to display, it appears that LyX's
conversion script calls ImageMagick, ImageMagick calls Ghostscript, and
Ghostscript hangs as if awaiting user input.
The only semi-rational explanation I can muster for this mix of symptoms
is that somewhere there is a string buffer overflowing when the file
names are too long, and that the the environment variables somehow
impact the capacity of that buffer.
Do any of the developers have any idea of a place where file paths/names
and environment variables might be sharing buffer space?
/Paul
