On Tue, 29 Jul 2003, David Woolley wrote: > > not exactly - since control/C would be caught by a signal handler, > > it would still interrupt whatever you're doing. And the signal handler > > couldn't do anything useful for prompting you. > > The normal expected behaviour for SIGINT on an interactive program is > to return to the basic command mode without losing state. SIGINT on > Lynx is very easy to hit by accident and throws away all state. The > function with the default binding of ^G is closer to what one would normally > expect from SIGINT.
it's closer, but doesn't really interrupt anything. One could (perhaps some code change needed - to make the two accessible) bind ^C to the same function. but that would leave no direct way to stop lynx (other than killing it from another terminal). -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
