On Thu, 18 Oct 2001, Angus Leeming wrote: [Symmetry.]
> I still don't buy this argument. It strikes me that if the controlling Well, I don't care much either way. Your solution is fine. > > What I would like to see is a process manager in LyX: In this dialog, you > > would have a list of all child-processes that LyX initiated. For each, you > > could see the invocation command, the status, and manually kill it. > > Again, this makes sense only for the case of Fork and NoWait. We don't know > the PID of the processes launched through system, and, anyway, all future > input is blocked if we Wait. Hmm, is it not possible to get the PID of child-processes from system in some way or another? Maybe not. So be it. > My idea is to create a new shellstream class. The converters would create a > small shell script, possibly involving multiple conversions. This would be > launched as a forked process runnind asynchronously. When the shell script > was finished and the conversion to the final form had been completed, the > ForkedcallController would call the callback function and we could, for > example, launch the viewer or load the graphics into LyX. Sounds good to me. If you go all the way and do the pipe stuff as well, maybe you could also have a look and see if some of the external material insets could do without the Python scripts? There is a wrapping Python script which basically is a safe mini-shell with input/output redirection that uses execvp. Greets, Asger
