From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: follow-up & CC
Date: Wed, 12 Nov 2003 21:00:06 +0100 [thread overview]
Message-ID: <v9ptfx5pdl.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <un0b1e8nv.fsf@gnu.org>
On Wed, Nov 12 2003, Sam Steingold wrote:
>> * Reiner Steib <4.hpr.03.e.f@aheshrefcnz.qr> [2003-11-12 17:54:10 +0100]:
[...]
>> But if you (or anyone else) want to implement such checks in
>> `message-carefully-insert-headers'... ;-)
>
> Patch appended.
When following up to my previous message...
,----
| Newsgroups: gmane.emacs.gnus.general
| Message-ID: <v94qx97cjx.fsf@marauder.physik.uni-ulm.de>
| Reply-To: reiner.steib@gmx.de
| Mail-Followup-To: ding@gnus.org
| Original-To: ding@gnus.org
| Mail-Copies-To: nobody
`----
... and using `message-insert-wide-reply' (`C-c C-f w'), I get a
failing (string-match "ding@gnus.org" nil) here:
+ for old-header = (mail-fetch-field (symbol-name synonym))
+ when (string-match new-header old-header)
"ding@gnus.org" comes from "Mail-Followup-To:" (I replied "yes"
when asked about obeying MFT).
Is this the correct fix? Can `new-header' ever be nil?
| for old-header = (mail-fetch-field (symbol-name synonym))
| when (and new-header old-header
| (string-match new-header old-header))
BTW, suggestions for a doc-string for
`message-carefully-insert-headers', anyone?
>> I will change `gnus-message 3' to `message'. `message.el' is supposed
>> to be independent from Gnus. Thanks for pointing this out.
>
> actually, message.el autoloads quite a few gnus-util.el and other
> functions.
Yes, but I don't intend to make this situation worse. `gnus-message'
hasn't been used before there.
(Maybe someday we will factor out stuff from `gnus-util.el' used in
`message.el' to, say `msg-util.el' and require it from Gnus and
Message.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-11-12 20:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 1:18 Sam Steingold
2003-11-10 12:30 ` Reiner Steib
2003-11-10 14:47 ` Sam Steingold
2003-11-10 17:44 ` Reiner Steib
2003-11-10 18:04 ` Sam Steingold
2003-11-10 18:54 ` Reiner Steib
2003-11-10 19:12 ` Sam Steingold
2003-11-10 19:26 ` Sam Steingold
2003-11-10 20:26 ` Reiner Steib
2003-11-12 16:05 ` Sam Steingold
2003-11-12 16:54 ` Reiner Steib
2003-11-12 18:36 ` Sam Steingold
2003-11-12 20:00 ` Reiner Steib [this message]
2003-11-12 21:13 ` Sam Steingold
2003-11-18 16:05 ` Reiner Steib
2003-11-18 18:50 ` Sam Steingold
2003-11-18 19:57 ` Reiner Steib
2003-11-18 20:47 ` Sam Steingold
2004-01-03 14:07 ` Reiner Steib
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=v9ptfx5pdl.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).