I have been helping a user debug a problem with a tool (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, 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
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 am not that familiar with Windows. Perhaps there is a security setting that interferes with pipe operation?
