Arnd Hanses wrote:
> 
> On 31 Aug 1999 17:57:55 +0200, Lars Gullik Bj°nnes wrote:
> 
> >Stephan Witt <[EMAIL PROTECTED]> writes:
> >
> >| LaTeX and Xdvi are children of LyX and directed by LyX to the
> >| internally computed hidden tmp-directory. I'm aware of that
> >| effect: If I close a file and reopen it again, then I have to
> >| close my running Xdvi too, because it is useless now, when using
> >| update->dvi. If I start Xdvi again it works ok. But there is no
> >| mystery. LyX creates a new tmp-directory (as I can see with /bin/ls)
> >| and starts working there. The update-dvi operation creates the
> >| new dvi file in the new tmp-dir.
> >|
> >| latex doesn't delete and recreates the dvi file,
> >| the contents of the dvi file will be replaced by latex/tex.
> >
> >Yes, and this should be now problem. Xdvi should not care (too much)
> >that the file it views suddenly disappears. Ok, the xdvi is now
> >defunct. Do you mean that it would be better if LyX killed the xdvi
> >when it destroys teh buffer?
> 
> IMHO killing before any defunct is the cleanest solution and avoids
> problems.
> 
> Otherwise you'll leave behind abandoned zombie-like processes haunting
> your box (shudder :-)
> 

Sorry for the late response. I was 2 days not online (travelling to customer).

I don't think it's a real problem with "zombie-like" running xdvi's.

1. You can see them.
   You can regularily quit them.
   You can decide yourself when to do so.
2. If I quit LyX, then Xdvi is left running too and I'm sure there're
   users who wants to leave this behaviour untouched.

A possible solution may be
1. to document the current behaviour and/or
2. kill (with asking the user?) the running "defunct" xdvi and start a new one
   when the user selects "View->dvi" or "Update->dvi" from menu

Greets,

Stephan Witt

---------------------------------------------------------------
<[EMAIL PROTECTED]>  | beusen unternehmensgruppe senkel
fon: +49 30 549932-62     | Landsberger Allee 392
fax: +49 30 549932-29     | 12681 Berlin, Germany
---------------------------------------------------------------

Reply via email to