> Someone else might have a better answer, but the only thing I know to do
> here is to attach a debugger, such as gdb, to the running process, and then
> you can see the output there. This seems overkill, however, and it will slow
> LyX down.
> Another option would be to run LyX from a script that redirected stderr to a
> file, and then you could always look at that file if you needed to do so.
> E.g.:
> #!/bin/bash
> /usr/bin/lyx $@ 2>&1 >/tmp/lyx-output
> Put that into /usr/local/bin/lyx, say, and it will get run instead of
> /usr/bin/lyx (assuming your PATH says so). Then if you want to see the
> terminal output, you can do:
> u...@host> tail -f /tmp/lyx-output
> And you can of course look back at anything that went by before this way,
> too.

Thanks very much, rh.

I got the second option to work, and it is essentially what I was
looking for.  Interesting!  it is sort of like a .log file for the LyX
process.  I wonder, is there a similar procedure for MS-Windows?  What
would it be?


Reply via email to