Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!decvax!decwrl!sun!guy From: guy@sun.uucp (Guy Harris) Newsgroups: net.unix Subject: Re: '#' as comment character vs. '#' as erase character Message-ID: <2396@sun.uucp> Date: Mon, 8-Jul-85 06:37:08 EDT Article-I.D.: sun.2396 Posted: Mon Jul 8 06:37:08 1985 Date-Received: Thu, 11-Jul-85 00:22:08 EDT References: <291@ucdavis.UUCP> <2401@pegasus.UUCP>, <2360@sun.uucp> <5750@utzoo.UUCP> <11388@brl-tgr.ARPA> Organization: Sun Microsystems, Inc. Lines: 22 > > > 2) Why were the '#' and '@' characters used as editing characters, > > > other than nostalgia for Multics (which used lots of weird IBM > > > 2741 printing terminals over half-duplex lines, and couldn't > > > do much better)... > > > The older UNIXes in cooked mode would echo everything one typed, > including control characters. About the only safe characters to > use for "magic" things were printable characters such as \ # @. > This works out better on hardcopy terminals, too, which is what > most of the original UNIX terminals were. OK, then, we rephrase the question as "why did the older UNIXes echo everything one typed?" The DEC OSes which echoed things sanely already existed - they even handle hardcopy terminals about as well as one can (they echo the characters being erased between backslashes). The policy of echoing things blindly also forced the policy of suppressing the output of the EOT character, which policy tends to upset certain terminals which accept positioning information in the form of 7-bit binary numbers (yes, that's dumb, but those terminals do exist and we had to deal with them at CCI). Guy Harris