From: Daniel Dehennin <daniel.dehennin@baby-gnu.org>
To: ding@gnus.org
Subject: Re: [PATCH] Use `gnus-parameters' in `gnus-group-split-fancy'
Date: Sat, 01 Feb 2014 14:04:54 +0100 [thread overview]
Message-ID: <87txcjyoeh.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <87ob2rhdi7.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Fri, 31 Jan 2014 16:40:00 -0800")
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Daniel Dehennin <daniel.dehennin@baby-gnu.org> writes:
>
>> This version of the patch[1] fixes two problems of the previous one:
>>
>> 1. some SPLIT where duplicated because the group name was present in
>> “gnus-newsrc-alist” and in “gnus-parameters”
>>
>> 2. using only groups from “gnus-newsrc-alist” avoid creating new ones
>> automatically when splitting, now, a user just need to:
>> 1. add a new entry to “gnus-parameters”
>> 2. update “nnmail-split-fancy” with “gnus-group-split-update”
>> 3. subscribe to the new mailing list
>> 4. the splitting will create the new group automatically when the
>> first mail arrives
>
> Thanks; I've now applied this to Ma Gnus 0.10. Perhaps something needs
> to be documented in the manual, too?
I don't think, because the documentation of Group Mail Splitting already
says it use Group parameters.
I mostly consider this as a fix to behave like described in the
documentation ;-)
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x7A6FE2DF
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
next prev parent reply other threads:[~2014-02-01 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 14:27 Daniel Dehennin
2013-12-28 1:17 ` Daniel Dehennin
2014-01-02 22:43 ` Daniel Dehennin
2014-01-04 14:55 ` Steinar Bang
2014-01-04 21:40 ` Daniel Dehennin
2014-01-05 5:13 ` Steinar Bang
2014-01-05 5:33 ` Daniel Dehennin
2014-01-05 13:03 ` Steinar Bang
2014-02-01 0:40 ` Lars Ingebrigtsen
2014-02-01 13:04 ` Daniel Dehennin [this message]
2014-02-01 20:39 ` Lars Ingebrigtsen
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=87txcjyoeh.fsf@hati.baby-gnu.org \
--to=daniel.dehennin@baby-gnu.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).