From: Chris Siebenmann <cks>
To: rc
Subject: Re: Another vote for a built-in read function
Date: Fri, 17 Sep 1993 12:58:00 -0400 [thread overview]
Message-ID: <93Sep17.125807edt.2062@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: gjv%atlas%cesar's message of Fri, 17 Sep 93 09:10:54 -0400. <9309171315.AA21670@SINet.SLB.COM>
The last thing rc needs is MORE quoting. One of the core design features
is that the quoting rules are simple, regular, predictable, and minimal;
adding \ as another quoting operator is none of the above. If we're going
to make any changes to quoting, we should remove \'s special magic at the
end of lines.
- cks
next prev parent reply other threads:[~1993-09-17 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-17 13:10 gjv%atlas%cesar
1993-09-17 16:58 ` Chris Siebenmann [this message]
1993-09-17 18:17 gjv%atlas%cesar
1993-09-17 19:29 Tom Culliton x2278
1993-09-17 23:18 ` Scott Schwartz
1993-09-19 19:59 Tom Culliton x2278
1993-09-20 2:44 ` Scott Schwartz
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=93Sep17.125807edt.2062@hawkwind.utcs.toronto.edu \
--to=rc@hawkwind.utcs.toronto.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).