From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] docs vs code
Date: Wed, 12 Jan 2005 19:31:47 -0500 [thread overview]
Message-ID: <ee9e417a05011216317ae2a3b0@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.58.0501061522080.10670@malasada.lava.net>
> Ugh! I read the manual page online:
>
> A type of ­1 enables the connection to receive copies of packets of
> all types. A type of ­2 enables the connection to receive copies of
> the first 64 bytes
>
> and the ­ isn't rendered as anything visible. *sigh*.
Fixed. Apprently ­ is now a discretionary dash.
I changed them to –, which is clearly "correct"
though somehow it seems to end up smaller than just
a "-" on my screen.
Russ
next prev parent reply other threads:[~2005-01-13 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 20:23 Tim Newsham
2005-01-06 21:06 ` Charles Forsyth
2005-01-07 1:22 ` Tim Newsham
2005-01-13 0:31 ` Russ Cox [this message]
2005-01-13 3:00 ` Thomas
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=ee9e417a05011216317ae2a3b0@mail.gmail.com \
--to=russcox@gmail.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).