From: Callum Gibson <callum.gibson@db.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: $^t
Date: Mon, 3 Sep 2001 23:16:27 -0500 [thread overview]
Message-ID: <200109040316.f843GRP17441@merton.aus.deuba.com> (raw)
In-Reply-To: <200109040143.f841ht416783@rakitzis.com> from "byron@rakitzis.com" at Sep 03, 2001 09:43:55 PM
byron@rakitzis.com writes:
}That being said now that Plan 9 is more open perhaps the more
}superficial incompatabilities should be normalized, if possible.
FWIW, I think $^t is more logical since it conserves special chars, even
if it reverses the sense of the ^ operator.
(c)2001 Callum Gibson callum.gibson@db.com
Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620
### The opinions in this message are mine and not Deutsche's ###
next prev parent reply other threads:[~2001-09-04 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 2:43 $^t Byron Rakitzis
2001-09-04 4:16 ` Callum Gibson [this message]
2001-09-05 4:37 ` $^t Paul Haahr
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 9:20 $^t Matt
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=200109040316.f843GRP17441@merton.aus.deuba.com \
--to=callum.gibson@db.com \
--cc=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).