On 07/31/2018 10:36 PM, Will S wrote: > I have been helping a user debug a problem with a tool (LyZ, > https://github.com/willsALMANJ/lyz > <https://github.com/willsALMANJ/lyz>) that I maintain that interfaces > with LyX through the LyX server. The main symptom is that the > lyxserver.out file appears to be empty. Specifically, when LyZ writes > a command into lyxserver.in <http://lyxserver.in>, LyX performs that > command as normal (so the "statistics" command causes the statistics > window to pop up in LyX), but when a command (like > "server-get-filename") is run that requires a response from LyX that > response does not get written to lyxserver.out (lyxserver.out still > appears empty). This problem is seen on some Windows systems but not > all. More details about the specific issue can be found at this page: > https://github.com/willsALMANJ/lyz/issues/14 >
Just so it doesn't get lost, you might file a parallel bug for LyX. > Are there any techniques we could use to debug this issue further? It > seems that the command line flags do not work on Windows so we can't > enable debug output at startup. I thought that might useful to see if > an hour occurs when lyxserver.out is created at start up. We have > opened the messages window and seen "LyXComm: Error sending message:" > but by the time we open this window it is too late to see messages > related to startup errors. Is there something else that we could try? I think the solution is to build LyX so that it launches a console window when it starts. There are weird issues here about how Windows writes to stderr, etc. I can build such a binary easily enough and post it somewhere for your user to install, if that seem sensible, though it may take a few days. I accidentally built such a thing when I was starting to build the new Windows installer.... Riki
