From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9b142a6f9735566373de4e125f1beb2c@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam command language
From: Richard Miller <miller@hamnavoe.demon.co.uk>
In-Reply-To: <2vidnbnNi9JlfhmiU-KYgw@comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu,  9 Oct 2003 10:18:44 +0100
Topicbox-Message-UUID: 698e09e8-eacc-11e9-9e20-41e7f4b1d025

> I also forgot about the terminal driver, which in some
> incarnations defaulted to \ as an escape character,

My first experience of Unix (circa 1976) was on an uppercase-only
terminal.  The driver would display lowercase characters as
uppercase, and uppercase characters escaped with a backslash;
keyboard input was the inverse of this.  So it was a common
mistake to type something like this in a C program
	PRINTF("\HELLO, WORLD\N"):
which would result in "Hello, worldN" and no newline.

Exercise for the reader: how many backslashes are required
in the ed 's' command to correct the error?