From: lars@nocrew.org (Lars Brinkhoff)
Subject: [TUHS] The ^ = | ?
Date: 24 Jan 2003 08:07:33 +0100 [thread overview]
Message-ID: <854r7z9gay.fsf@junk.nocrew.org> (raw)
In-Reply-To: <200301240537.h0O5bjd60797@minnie.tuhs.org>
Warren Toomey <wkt at minnie.tuhs.org> writes:
> From my memory of Salus' book, the > syntax was relaced by ^, but
> when Ken went to the U.K to give a talk, he made the decision to
> switch over to the | symbol.
>
> Anyway, I could be completely wrong about this being in Salus'
> book, so if I am, I'll have to hunt down where this info came from.
You are right. Pages 51-53 (in the 1995 reprint).
--
Lars Brinkhoff http://lars.nocrew.org/ Linux, GCC, PDP-10,
Brinkhoff Consulting http://www.brinkhoff.se/ HTTP programming
next prev parent reply other threads:[~2003-01-24 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:09 Norman Wilson
2003-01-24 5:37 ` Warren Toomey
2003-01-24 7:07 ` Lars Brinkhoff [this message]
2003-01-24 10:32 ` Sven Mascheck
2003-01-26 1:40 ` Greg Lehey
-- strict thread matches above, loose matches on Subject: below --
2003-01-25 8:46 Wolfgang Helbig
2003-01-24 2:09 Carl Lowenstein
2003-01-24 0:04 John Holden
2003-01-23 12:25 Lange, David
2003-01-24 0:05 ` M. Warner Losh
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=854r7z9gay.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
/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).