Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.tech Subject: Re: Pipes Message-ID: <12513@cbmvax.commodore.com> Date: 10 Jun 90 06:27:04 GMT References: <12391@cbmvax.commodore.com> <1990Jun7.215928.3826@cbnewsm.att.com> <5795@sugar.hackercorp.com> <1990Jun9.062243.24641@cbnewsm.att.com> Reply-To: jesup@cbmvax (Randell Jesup) Distribution: na Organization: Commodore, West Chester, PA Lines: 31 In article <1990Jun9.062243.24641@cbnewsm.att.com> nsw@cbnewsm.att.com (Neil Weinstock) writes: > In an ideal world, the terminal driver would provide the same type of > line editing as one's favorite editor. > >If I were feeling ambitious, I would generalize that statement to include >string gadgets, and just about everything else. Well, we're getting closer, what with string gadget editing hooks. >BTW, one problem with this approach is that the terminal driver doesn't know >the difference between a shell command and any other random keyboard input. >This screws up the history mechanism somewhat, since one would usually prefer >the shell history to include only shell commands. Is there an obvious fix >for this? After about 30 seconds of thought, all I can come up with is to >allow the shell (or any application) to control which history buffer >is used by the terminal driver (using escape codes, or something like that). History and related items (such as filename expansion) are the tough parts of doing console handlers, if you want to go that route. >And now for YAHBI (Yet Another Half-Baked Idea): a linedit.library, to be >used, at the minimum, by the console.device. Comments? console.device has nothing to do with editing, you want console-handler. :-) Not for 2.0. If we do it, it would be best to integrate it with the default Intuition string editing hook somehow. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"