Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!cica!iuvax!purdue!decwrl!bacchus.pa.dec.com!granite.pa.dec.com!mwm From: mwm@raven.pa.dec.com (Mike (Real Amigas have keyboard garages) Meyer) Newsgroups: comp.sys.amiga.tech Subject: Re: Pipes Message-ID: Date: 12 Jun 90 19:02:19 GMT References: <12391@cbmvax.commodore.com> <1990Jun7.215928.3826@cbnewsm.att.com> <5795@sugar.hackercorp.com> <1990Jun9.062243.24641@cbnewsm.att.com> Sender: news@wrl.dec.com (News) Distribution: na Organization: Missionaria Phonibalonica Lines: 22 In article <1990Jun9.062243.24641@cbnewsm.att.com> nsw@cbnewsm.att.com (Neil Weinstock) writes: 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. One might, but I wouldn't. Of course, I don't want a "shell history"; I want an "input history". That way, I get access to the everything I typed, and not just that which is saved by a some specific subsystem. It also means I get a consistent history mechanism for all CLI-based programs. Of course, I also want to be able to select input from all text output into the CLI, but that's a different problem.