From: Dennis Ritchie <dmr@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam command language
Date: Thu, 9 Oct 2003 20:26:08 -0400 [thread overview]
Message-ID: <73afeaa26bd3f166bde71fb190f73ea3@plan9.bell-labs.com> (raw)
> 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?
Years ago I ran into a situation with a script
(probably involving all of the shell, ed, and troff)
in which N½ \ were needed. N was too few, N+1 were
too many.
Dennis
next reply other threads:[~2003-10-10 0:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 0:26 Dennis Ritchie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 19:16 Scott Schwartz
2003-10-07 19:20 ` rob pike, esq.
2003-10-08 8:37 ` Douglas A. Gwyn
2003-10-08 15:42 ` rob pike, esq.
2003-10-09 8:42 ` Douglas A. Gwyn
2003-10-09 9:18 ` Richard Miller
2003-10-09 15:01 ` rog
2003-10-07 8:58 steve.simon
2003-10-07 9:38 ` Axel Belinfante
2003-10-04 1:53 [9fans] Newbie: life without rio rob pike, esq.
2003-10-06 12:52 ` [9fans] sam command language rog
2003-10-06 15:08 ` Rob Pike
2003-10-06 15:55 ` Jim Choate
2003-10-06 16:35 ` Micah Stetson
2003-10-06 16:41 ` Rob Pike
2003-10-06 16:47 ` Micah Stetson
2003-10-06 18:24 ` boyd
2003-10-07 18:34 ` rog
2003-10-07 18:48 ` rob pike, esq.
2003-10-08 14:44 ` rog
2003-10-08 15:09 ` Jim Choate
2003-10-09 0:52 ` okamoto
2003-10-08 15:46 ` rob pike, esq.
2003-10-09 17:35 ` rog
2003-10-07 20:16 ` vdharani
2003-10-07 18:59 ` Russ Cox
2003-10-08 14:33 ` rog
2003-10-08 14:44 ` Derek Fawcus
2003-10-08 15:27 ` Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73afeaa26bd3f166bde71fb190f73ea3@plan9.bell-labs.com \
--to=dmr@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).