Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!wuarchive!texbell!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Pipes
Message-ID: <5807@sugar.hackercorp.com>
Date: 10 Jun 90 02:09:25 GMT
References: <12391@cbmvax.commodore.com> <1990Jun7.215928.3826@cbnewsm.att.com> <5795@sugar.hackercorp.com> <1990Jun9.062243.24641@cbnewsm.att.com>
Reply-To: peter@sugar.hackercorp.com (Peter da Silva)
Distribution: na
Organization: Sugar Land Unix - Houston
Lines: 32

In article <1990Jun9.062243.24641@cbnewsm.att.com> nsw@cbnewsm.att.com (Neil Weinstock) writes:
> If I were feeling ambitious, I would generalize that statement to include
> string gadgets, and just about everything else.
  ^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Damn good point. Yes.

> one would usually prefer
> the shell history to include only shell commands.

Not always. But usually, yes.

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

Sounds good. You could even put this sequence in your prompt, & alias your long
running commands to "echo esc; command" to turn off history.

I'd also like escape sequences to change window borders, create menu entries,
change the window title, etcetera.

> And now for YAHBI (Yet Another Half-Baked Idea):  a linedit.library, to be
> used, at the minimum, by the console.device.  Comments?

I like it.
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ My other car is a hot-air balloon.
      v  "Have you hugged your wolf today?" `-_-'