From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: message-alternative-emails
Date: Sun, 02 Jan 2011 08:37:17 +0100 [thread overview]
Message-ID: <m339pbg3iq.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <mailman.4.1293039909.895.info-gnus-english@gnu.org>
Yuri D'Elia <wavexx@users.sf.net> writes:
> In my .gnus file I have the following:
>
> (setq message-alternative-emails
> (concat
> "\\(email\\)\\|" ...
> "\\(email\\)\\|" ... ))
>
> (setq message-dont-reply-to-names
> (concat
> "\\(" (regexp-quote user-mail-address) "\\)\\|"
> message-alternative-emails))
>
> (setq gnus-ignored-from-addresses message-dont-reply-to-names)
>
> It sounds like there should be a way to avoid all that repetition. Why
> aren't these variables derived from each-other automatically by default?
The last variable is derived from `user-mail-address'. The first second
wouldn't make sense to derive from the first, I think.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next parent reply other threads:[~2011-01-02 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4.1293039909.895.info-gnus-english@gnu.org>
2011-01-02 7:37 ` Lars Magne Ingebrigtsen [this message]
2011-01-02 10:41 ` message-alternative-emails Yuri D'Elia
[not found] ` <mailman.2.1293964919.24794.info-gnus-english@gnu.org>
2011-01-02 19:20 ` message-alternative-emails Lars Magne Ingebrigtsen
2010-12-22 17:42 message-alternative-emails Yuri D'Elia
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 22:09 message-alternative-emails Olivier Sirven
2009-08-12 22:42 ` message-alternative-emails Mark T.B. Carroll
2009-08-13 7:03 ` message-alternative-emails Olivier Sirven
2009-08-13 13:29 ` message-alternative-emails Mark T.B. Carroll
2009-08-13 7:23 ` message-alternative-emails Nicolas KOWALSKI
[not found] ` <mailman.4505.1250148230.2239.info-gnus-english@gnu.org>
2009-08-13 8:09 ` message-alternative-emails Olivier Sirven
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=m339pbg3iq.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.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).