Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.unix.questions
Subject: Re: Strangeness in shell
Message-ID: <5404@ficc.uu.net>
Date: 1 Aug 89 13:45:05 GMT
References: <432@mccc.UUCP> <9700009@osiris.cso.uiuc.edu> <2277@auspex.auspex.com> <10639@smoke.BRL.MIL>
Organization: Xenix Support, FICC
Lines: 24

In article <10639@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
> -In article <5275@ficc.uu.net>, peter@ficc.uu.net (Peter da Silva) writes:
> -> The right place for ksh -type command line editing is in the terminal
> -> driver or xterm!

> Some of us think the right place is in the terminal!

That's the moral equivalent of the terminal driver. My Amiga gives me this
sort of capability, via cut and paste with the mouse, as do other people's
Macs and Atari STs if they have any sort of decent terminal program (when
I had an ST, I didn't, but that was a long time ago and I don't hold that
agin it).

The one problem with this approach is that you really should only maintain
a command line history when you're in canonical mode (ICANON, or COOKED).
You don't want your vi or emacs commands messing up your buffer. I guess
you could modify the termcap for your terminal to turn buffering off and
on when you enter or leave a screen-oriented program... (goes off muttering
about VS and VE...)
-- 
Peter da Silva, Xenix Support, Ferranti International Controls Corporation.
Business: peter@ficc.uu.net, +1 713 274 5180. | "The sentence I am now
Personal: peter@sugar.hackercorp.com.   `-_-' |  writing is the sentence
Quote: Have you hugged your wolf today?  'U`  |  you are now reading"