From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Grammar error in mc(1)?
Date: Mon, 28 Oct 2002 15:49:12 -0500 [thread overview]
Message-ID: <0425de6dc8fc2c46b9b10c615c713914@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 64 bytes --]
It probably once said, "If run in an 8½(1) window..."
-rob
[-- Attachment #2: Type: message/rfc822, Size: 1625 bytes --]
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Grammar error in mc(1)?
Date: Mon, 28 Oct 2002 15:45:50 -0500 (EST)
Message-ID: <200210282045.g9SKjoE18042@augusta.math.psu.edu>
Shouldn't the sentence, ``If run in an rio(1) window...'' be, ``If run
in a rio(1) window..'' ? Not a big deal at all, but just something I
noticed.
- Dan C.
next reply other threads:[~2002-10-28 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 20:49 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 20:45 Dan Cross
2002-10-29 9:53 ` Douglas A. Gwyn
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=0425de6dc8fc2c46b9b10c615c713914@plan9.bell-labs.com \
--to=rob@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).