Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!mandrill!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon S. Allbery)
Newsgroups: comp.unix.wizards
Subject: Re: Input Line Editing
Message-ID: <11947@ncoast.UUCP>
Date: 24 Jul 88 02:44:14 GMT
References: <16456@brl-adm.ARPA> <9666@eddie.MIT.EDU> <10443@ulysses.homer.nj.att.com> <9671@eddie.MIT.EDU> <23839@bu-cs.BU.EDU> <6192@bloo <9677@eddie.MIT.EDU>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.unix.wizards
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 31

As quoted from <9677@eddie.MIT.EDU> by nessus@wonko.MIT.EDU (Doug Alan):
+---------------
| > From: henrik@blblbl.UUCP (Larry DeLuca)
| > While it's not going to help the ile people much, it still seems the
| > best place for a line editor of some sort is still the tty driver
| > (ioctl's can be used to set characters or toggle between modes).
| 
| No, you're wrong.
+---------------

Strong disagreement.  Given a STREAMS-based tty driver, one could push the
following modules:

	terminfo-like module (or termcap, depending on your prejudices)
	input line editor module
	output module -- replaces more, etc.

The TLM would be able to accept a term{cap,info} entry by grabbing an ioctl
(or whatever; my STREAMS guide is still on order) with the data in it.  The
user could push their own choice of input and output filters (vi/emacs, more/
less) or leave off either or both.  Then programs could do "smart" screen
I/O via ioctls or etc. (or even by canonical escape sequences, as with the
existing SysV facilities -- not that I've ever seen a SysV kernel with any
of the virtual terminals actually compiled in) processed by the TLM.

To the person who wants a "dumb X" -- isn't that what "window" is?

++Brandon
-- 
Brandon S. Allbery, uunet!marque!ncoast!allbery			DELPHI: ALLBERY
	    For comp.sources.misc send mail to ncoast!sources-misc