From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mail 'Q' reply
Date: Wed, 9 Oct 2002 13:08:55 +0100 [thread overview]
Message-ID: <77c932e3be1e5ac4d3718a8490860d02@vitanuova.com> (raw)
i have a trio of commands i use for this sort of thing, quote (similar
to dmr's mindent); and a+, and a- which add or remove an arbitrary string
from the start of lines (default tab).
i find the short names useful to avoid filling up the already crowded
acme tag space.
> Doesn't help with translation, of course.
it seems to me that mail system could look for a "Charset:" or
"Content-Type" header on the outgoing mail and translate from utf-8
accordingly, much as it does for "Attach:" headers in acme.
cheers,
rog.
next reply other threads:[~2002-10-09 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 12:08 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 3:25 okamoto
2002-10-09 3:13 Dennis Ritchie
2002-10-09 2:35 YAMANASHI Takeshi
2002-10-07 1:26 YAMANASHI Takeshi
2002-10-06 22:05 Skip Tavakkolian
2002-10-06 20:42 rob pike, esq.
2002-10-06 18:11 Skip Tavakkolian
2002-10-05 12:18 rob pike, esq.
2002-10-05 3:29 Skip Tavakkolian
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=77c932e3be1e5ac4d3718a8490860d02@vitanuova.com \
--to=rog@vitanuova.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).