From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: message-reply-to-function bug?
Date: 19 May 2000 15:21:18 -0400 [thread overview]
Message-ID: <5b7lcqe47l.fsf@heart.cs.rochester.edu> (raw)
In-Reply-To: Dmitry Yaitskov's message of "19 May 2000 15:07:07 -0400"
>>>>> "Dmitry" == Dmitry Yaitskov <dimas@home.com> writes:
Dmitry> Note the phrase "As you can see, this function should return a string
Dmitry> if it has an opinion as to what the To header should be." Where does
Dmitry> it say anything about a list?
Dmitry> (Perhaps my info entry is outdated... is it?)
>> [...]
>>
Dmitry> Which looks like a bug, at least in the docs. The following version
Dmitry> works though:
>>
Dmitry> (setq message-reply-to-function
Dmitry> (lambda ()
Dmitry> (cond ((equal (mail-fetch-field "reply-to") "qq@aa.com")
Dmitry> (list (cons 'To (mail-fetch-field "from"))))
Dmitry> (t
Dmitry> nil))))
>>
>> This function returns a list of headers.
Oops, I thought it is in gnus.texi. OK, now it is fixed.
Shenghuo
prev parent reply other threads:[~2000-05-19 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 15:11 Dmitry Yaitskov
2000-05-19 15:39 ` Shenghuo ZHU
2000-05-19 19:07 ` Dmitry Yaitskov
2000-05-19 19:21 ` Shenghuo ZHU [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=5b7lcqe47l.fsf@heart.cs.rochester.edu \
--to=zsh@cs.rochester.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).