On Tue, Dec 11, 2007 at 03:50:48PM +0100, Abdelrazak Younes wrote: > Enrico Forestieri wrote: > > On Tue, Dec 11, 2007 at 02:30:25PM +0100, Abdelrazak Younes wrote: > > > >> Jürgen Spitzmüller wrote: > >>> Abdelrazak Younes wrote: > >>>> An external process can fail on any system, either waiting for a user > >>>> input or because of an infinite loop. That can be Latex or any other > >>>> tool (htlatex comes to mind). In case of failure there is no other > >>>> choice but to go to the console where lyx was started. > >>> I use my OS's (i.e. KDE's) process manager in such cases, which gives > >>> nice > >>> information about the status and the possibility to act accordingly. > >> It does only give you the possibility to kill the process and that is > >> not something typical user will do. Besides, the standard input/output > >> is not there. Even on linux if you started LyX by double-clicking some > >> icon the console output is hidden (it is available only at the console > >> which started the X11 server). So I don't really understand your > >> opposition. There is clearly a need for that kind of functionality. > > > > On *nix you can open a console terminal to see the output. > > I know but still, you have to restart lyx at the command line from this > console to see that.
No, every output from a program goes to the console, so you can open such a terminal even after having started a program from the GUI and still be able to see its output (if any). For example, you get a console terminal when passing the -C option to xterm, but this is typically done by the session manager. You simply choose from a menu something like "Open console" instead of "Open terminal". Details vary among the various desktop environments or window managers, but I have yet to see a setup that doesn't offer this possibility. > > Even on > > Windows an option culd be added to the launcher such that the console > > is not hidden. > > The beauty of current solution is that the standard output is redirected > and you don't need to restart LyX. With this in place we can start to > compile LyX as a GUI application instead of a console application. You think in Windows terms. There's no distinction between GUI or console application on *nix. Then, I don't think that transforming LyX in a GUI application on Windows is so desirable, because you simply lose stdin, stdout, and stderr, and thus the possibility of tracking the output of the launched applications (unless some weird trickery is used, which I do not recommend). > > Note that with the change from \batchmode to \nonstopmode the chance > > of a stalled latex (and a hanging lyx) is high, because when a file > > that should be included is not found, latex stops, expecting you to > > enter a new filename. > > Has this changed recently? It's done in the patch by Peter. -- Enrico
