From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: carry over headers into reply
Date: Sun, 03 Jun 2012 17:05:01 +0800 [thread overview]
Message-ID: <87ipf8ix4y.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87zk8l9b13.fsf@ericabrahamsen.net>
On Sat, Jun 02 2012, Eric Abrahamsen wrote:
> I've been trying for a while to figure out how to draw the value of a
> custom header from an edited mail message (the header inserted via
> another function) and insert it into a reply to that message. I can't
> seem to find any hooks (or even efficient places to advise functions)
> that will let me slurp a header value from the original message, and
> then place it in the reply that's being composed.
Answering my own question, `message-fetch-reply-field' does exactly
this.
--
GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
of 2012-06-01 on pellet
Ma Gnus v0.6
prev parent reply other threads:[~2012-06-03 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 12:02 Eric Abrahamsen
2012-06-03 9:05 ` Eric Abrahamsen [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=87ipf8ix4y.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).