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

[Cameron Patrick]

Thanks to everyone who replied to my questions --- it seems that there's
more complexity hidden in Linux's terminal handling than meets the eye (or
my eye, at any rate).

On Mon, 11 Nov 2002 10:18:21 +0800 (WST), Mike Holland wrote:

| 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.

Well, I just tested it then. Xemacs certainly doesn't ignore it on my
machine. Starting a copy of xemacs in the background and typing
kill -HUP %1 gives the following message:

> Fatal error (1).
>
> Your files have been auto-saved.
> Use `M-x recover-session' to recover them.

as well as about a page of random waffle and a backtrace.

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

I considered that before posting, but if it was stopped waiting for input,
wouldn't you expect to see some form of full-screen display first?  i.e.
before lynx waits for input, it pops up a message telling you it's loading
something from wherever it loads stuff from.

CP.