[plug] Xterms and bash and stuff: or, mysterious vanishing windows and mysterious vanishing stdin

[Mike Holland]

On Sat, 9 Nov 2002, Cameron Patrick wrote:

> programs launched in the background.  Most of the time, you can start an X
> program in the background by typing something like 'xemacs &' in an xterm,
> close the xterm, and the Xemacs will still be there[1].  Occasionally,
> though, it disappears in a puff of smoke and nothing is ever heard from it

As said, the shell sends a SIGHUP on exiting, but you would expect any X 
app to ignore that. I've never seen xemacs die that way. For a 
command-line app, you want it to die with the shell closes. Especially 
on a modem dial-in.

> Another curiosity I've noticed with bash's job control is that sometimes, a
> backgrounded program will be stopped if it wants to write to the screen,

I think you will find it really stopped because it is waiting on input, 
not output.

> but if you try something like 'mc &' or 'lynx &', you won't see a thing
> until you fg it.

Both of these read from the console.
 

-- 
        The origin of Truth is Doubt - Socrates