Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!sri-unix!sri-spam!mordor!lll-tis!ptsfa!dual!ucbvax!ATHENA.MIT.EDU!eichin From: eichin@ATHENA.MIT.EDU ("Mark W. Eichin") Newsgroups: comp.emacs Subject: termcap, flow control, emacs Message-ID: <8706211844.AA16179@FYUNCH.MIT.EDU> Date: Sun, 21-Jun-87 14:44:36 EDT Article-I.D.: FYUNCH.8706211844.AA16179 Posted: Sun Jun 21 14:44:36 1987 Date-Received: Tue, 23-Jun-87 00:43:46 EDT References: <1263@crash.CTS.COM> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 24 >From: Michael Ditto >Again, I feel that the ancient protocols should not be encouraged in any >new products. ... Later, > ... Also, part of the "definition" of an Emacs editor >is its "standard" Emacs command set as originally designed, and passed down >through the generations of hackers. Doesn't this make the emacs commandset one of these "ancient protocols"? ( :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) Really, wasn't one of the reasons for ^s/^q to be in-band was so that they could be generated by the user? At least in the CP/M micro world, they were used as flow control for the USER, not just the terminal. The standard way for a user to pause output in order to have time to read it was to hit ^s. Given the age of the 'emacs' series of editors, why did they overload ^s even further? RMS, Gosling, anyone out there know? I would guess it was simply mnemonic for 'Search', but what equipment of that day let them get away with it? /Happy Hacking........\\.............Mark Eichin/