Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!ulysses!cjc
From: cjc@ulysses.homer.nj.att.com (Chris Calabrese[rs])
Newsgroups: comp.unix.wizards
Subject: Re: Input Line Editing
Message-ID: <10448@ulysses.homer.nj.att.com>
Date: 14 Jul 88 14:53:20 GMT
References: <16456@brl-adm.ARPA> <9666@eddie.MIT.EDU> <59768@sun.uucp>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 22

In article <59768@sun.uucp>, guy@gorodish.UUCP writes:
> I don't know what "the built-in editor on the NeWS windowing system" is (I
> I assume that the editor on the "layers" system is similar, in concept, to the
> one in an EMACS or Andrew typescript window, in that it takes what you type and

Nope, they're not line editors, but simple cut-and-paste mouse operations
which allow the user to cut from anywhere on the screen (from any window)
and send that cut segment as a keyboard-like input to any window.  Since
this type of thing is 90% of what I use Ksh editing for, it is just fine
with me.  Also, it's real useful when editing multiple files with vi.

> > As for editors, I'd love to see one included in the terminal driver.
> 
> Gak.  *I*'d* love to see all line editing *removed* from the terminal driver,
> One advantage of *NOT* doing it in the kernel is that, as you pointed out, not
> everybody *does* want the same editor; if you put it in the kernel, users can't

I would like _vi_ in the kernel, but that's because
I like vi.  I guess I forgot the :-)'s.
-- 
	Christopher J. Calabrese
	AT&T Bell Laboratories
	ulysses!cjc