Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!boring!jack From: jack@boring.UUCP Newsgroups: net.arch Subject: Re: smarter terminal device drivers Message-ID: <6404@boring.UUCP> Date: Wed, 1-May-85 16:26:25 EDT Article-I.D.: boring.6404 Posted: Wed May 1 16:26:25 1985 Date-Received: Fri, 3-May-85 20:08:26 EDT References: <327@piggy.UUCP> <101@daisy.UUCP> <2048@uvacs.UUCP> Reply-To: jack@boring.UUCP (Jack Jansen) Organization: CWI, Amsterdam Lines: 31 Apparently-To: rnews@mcvax.LOCAL Providing multiple break/echo tables and transition rules isn't necesary if you delay echoing etc. until the character is being read. This doesn't mean that you have to wait until it is transferred to user space, only until the user program has done a read. Scenario : User Kernel User program. Type A Store it. Type B Store it. Read 80 chars, terminate on ' ' Echo A and B Type C Echo C and store it. Type ' ' Store ' ' and echo it. Copy 'ABC ' to user space. Wake user up. Note that it is debatable whether the space should be echoed. I think that it should, since the user program can make provisions not to echo it (assuming there are both an 'echo map' and a 'break map'. I think that delayed echo is usually a neat feature, since you can't mess up your screen by typing ahead to a program that doesn't expect it, and that it will easy the implementation of a break- and echo-map. -- Jack Jansen, {decvax|philabs|seismo}!mcvax!jack The shell is my oyster.