From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Usage of gnus mailing list mode
Date: Fri, 22 Aug 2008 12:45:35 +0200 [thread overview]
Message-ID: <87ej4hwcog.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <kztzddmmaa.fsf@kafka.physik3.gwdg.de> (David Engster's message of "Fri, 22 Aug 2008 11:28:13 +0200")
David Engster <deng@randomsample.de> writes:
Hi David,
>> Personally, I don't like it too much if people reply to my mailing
>> list articles to both me and the list. IMHO that's redundant and
>> annoying. Is that a convention and are there good reasons for such a
>> double-reply?
>
> AFAIK, that's what 'Mail-Followup-To' and 'Mail-Copies-To' headers are
> for (see mine). However, not many mail clients know them...
Ah, nice. I'll figure out how to add these headers to my own messages,
so that followups to me won't be duplicated.
>> If not, how do I teach gnus to put the mailing list in the To-header
>> and to omit the Cc (unless I do a wide reply).
>
> I don't think this is possible with only the 'to-list parameter being
> set. You could sync the 'to-address parameter with the 'to-list
> parameter in mailing-list mode. Not really nice, but this should work:
Hey, that looks quite good. Thanks a lot!
> (add-hook 'gnus-mailing-list-mode-hook
> (lambda ()
> (unless (gnus-group-get-parameter
> gnus-newsgroup-name 'to-address)
> (let ((to-list (gnus-group-get-parameter
> gnus-newsgroup-name 'to-list)))
> (when to-list
> (gnus-group-set-parameter gnus-newsgroup-name
> 'to-address to-list))))))
Bye,
Tassilo
next prev parent reply other threads:[~2008-08-22 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 14:55 Tassilo Horn
2008-08-22 9:28 ` David Engster
2008-08-22 10:45 ` Tassilo Horn [this message]
2008-08-22 11:32 ` Tassilo Horn
2008-08-22 11:58 ` David Engster
2008-08-22 13:40 ` Tassilo Horn
2008-08-22 13:59 ` David Engster
2008-08-29 4:52 ` Miles Bader
2008-08-29 7:12 ` Tassilo Horn
2008-08-31 3:32 ` Miles Bader
2008-09-01 7:06 ` Tassilo Horn
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=87ej4hwcog.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--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).