From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: forwarding messages when editing
Date: Tue, 14 Dec 1999 11:01:48 +1100 [thread overview]
Message-ID: <t4i1z8qtmoj.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Brian May's message of "Mon, 13 Dec 1999 16:58:34 +1100"
>>>>> "Brian" == Brian May <bmay@csse.monash.edu.au> writes:
Brian> have a look at the "S y" command, from the summary buffer.
Brian> Not sure if this requires supercite or not (I use
Brian> supercite).
Brian> This command will prompt you for a message buffer, and
Brian> automatically insert the cited version of the current
Brian> message at the current cursor position *in that buffer*.
Looks like I was partly mistaken here - I assumed that "S y" would
fetch the original article in raw mode (ie headers aren't filtered),
so that citations/references work properly, etc.
However, "S y" doesn't do this if the article has already been
fetched. In this case, you need to manually refetch it with "C-u g"
first.
A pity this isn't done by default... Perhaps this (IMHO) inconsistent
behaviour is a bug somewhere?
(Note: supercite will work without full header information, but cannot
supply full details for some styles, eg when the message-id is
required).
--
Brian May <bmay@csse.monash.edu.au>
prev parent reply other threads:[~1999-12-14 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 5:58 Brian May
1999-12-14 0:01 ` Brian May [this message]
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=t4i1z8qtmoj.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).