Xref: utzoo comp.sys.amiga:37742 comp.sys.amiga.tech:6442 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!agate!eris.berkeley.edu!mwm From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: My AmigaDOS 1.4 wishlist (one among thousands!) Keywords: list, dir, pipe:, loadwb, docs, rad1:, locks, selection, huge disks Message-ID: <26895@agate.BERKELEY.EDU> Date: 2 Aug 89 23:09:40 GMT References: <12878@well.UUCP> <12968@well.UUCP> Sender: usenet@agate.BERKELEY.EDU Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Organization: Missionaria Phonibalonica Lines: 37 In article <12968@well.UUCP> xanthian@well.UUCP (Kent Paul Dolan) writes: <[Following up my own posting; no class!] Nah, just lazy. No worse than me pickig up your posting to make my posting easier... Anyway, to add to the wish list: Unless I've broken things with a non-standard environment, currently C-c's only get sent to the process actually talking to the terminal. If that was started as one of a series by some program, then the program that did the starting doesn't see the signal, just the termination of the running program. If the broken (breaked?) program doesn't signal that it saw a break, or the program that started it doesn't check on these things (which it may be doing for good reason), then the next program in the series will be started. This is almost certainly not what the user wanted. The suggested behavior change is obvious: make C-c stop all programs involved. I would also suggest that C-d get the semantics that C-c has now, so that the user can stop only the current process, and the next one can continue if things are set up correctly (might as well do something with all those break characters). This should also affect a pipeline if the cli being used supports '|' pipes, so that C-c goes to all processes in the pipeline. Implementation: well, I can tell you how I'd tackle it, but I've been warped by watching how Unix does it, so I won't unless asked.