andy@polya.STANFORD.EDU (Andy Freeman) (03/02/88)
In article <877@astroatc.UUCP> johnw@astroatc.UUCP (John F. Wardale) writes: [Wardale suggests buffering output, shipping it close to display (e.g., to something upstream from terminal, and then go transfer char by char. Input "has" to be handled differently, unless program support, such as vi, is built into buffering agent. He's considering a controller, 8 ports, one 68k, which does the obvious things with a `loadable character-indexed "what-to-do" table.'] >This (of course) means that vi, emacs, jove, et-al. would have to >be hacked (alot ??) to take advantage of such things. Look at supdup, a protocol devised by Stallman (RMS of GNU fame) and documented in an AI lab tech report (it might be an LCS report). Not only does it work, and he's measured it, but he claims that it doesn't require much applications hacking. Of course, his "not much" may not agree with yours. -andy
daveb@geac.UUCP (David Collier-Brown) (03/03/88)
>In article <877@astroatc.UUCP> johnw@astroatc.UUCP (John F. Wardale) writes: >[Wardale suggests buffering output, shipping it close to display (e.g., > to something upstream from terminal, and then go transfer char by > char. Input "has" to be handled differently, unless program support, > such as vi, is built into buffering agent. In article <2099@polya.STANFORD.EDU> andy@polya.UUCP (Andy Freeman) writes: >Look at supdup, a protocol devised by Stallman (RMS of GNU fame) and >documented in an AI lab tech report (it might be an LCS report). Not >only does it work, and he's measured it, but he claims that it doesn't >require much applications hacking. The standard CCITT pads can also do about half of the work, by interactively setting/resetting the forward-on-character set, the forward-after-inactivity timeout and the local/remote echo bit. This works with the standard Emacs on Multics, and has for not less than 8 years. --dave (ryfm) c-b -- David Collier-Brown. {mnetor yunexus utgpu}!geac!daveb Geac Computers International Inc., | Computer Science loses its 350 Steelcase Road,Markham, Ontario, | memory (if not its mind) CANADA, L3R 1B3 (416) 475-0525 x3279 | every 6 months.
robert@pvab.UUCP (Robert Claeson) (03/05/88)
In article <2099@polya.STANFORD.EDU> andy@polya.UUCP (Andy Freeman) writes: >Look at supdup, a protocol devised by Stallman (RMS of GNU fame) and >documented in an AI lab tech report (it might be an LCS report). Encore has implemented a version of supdup in their Annex ethernet TCP/IP terminal server. And they do include a hacked version of GNU Emacs that uses the protocol (Encore calls it "leap" instead of "supdup"). It works just fine, but the start-up time increases, and you must specify leap mode when you start the editor. Otherwise GNU Emacs will do all editing by itself.
mac3n@babbage.acc.virginia.edu (Alex Colvin) (03/07/88)
Jim Perry at Dartmouth (now at Apollo?) and others implemented another remote editing protocol that ran in your Macintosh or Avatar (modified H19 with uC), sparing their poor Honeywell mainframes a lot of work. If done right, this gives you a screen editor that's relatively portable (e.g., talks to ED-like editors, which are found eveywhere). It also keeps the display from getting out of sync with the editing (e.g., the line you deleted on the display wasn't the one that was supposed to be there).