Gnus development mailing list
 help / color / mirror / Atom feed
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, 28 Dec 2013 02:17:18 +0100	[thread overview]
Message-ID: <87k3epg4f5.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <87fvpvbj8k.fsf@hati.baby-gnu.org> (Daniel Dehennin's message of "Sat, 14 Dec 2013 15:27:39 +0100")

[-- Attachment #1: Type: text/plain, Size: 2285 bytes --]

Daniel Dehennin <daniel.dehennin@baby-gnu.org> writes:

> Hello,
>
> I use a little patch[1] since years to split groups not only on group
> parameters from “newsrc” but from “gnus-parameters” too.
>
> I found the later easier to manage.
>
> Following is my pull request, if you want it.

Hello,

I rebase my patch[1] on latest master and use Gnus utility function
“gnus-group-find-parameter” instead of defining a useless new one.

Regards.

Here is my pull request.

The following changes since commit 934f25f8d8801afe315722fd0b0b4ea14bcb1534:

  Make split tracing work in nnimap groups, too (2013-12-26 17:39:39 +0100)

are available in the git repository at:

  git://git.baby-gnu.net/gnus.git tags/feature/use-gnus-parameters-in-gnus-group-split-fancy

for you to fetch changes up to a33cd267a99c690416b290beb3c37a3e65e19a15:

  Use `gnus-parameters' in `gnus-group-split-fancy' (2013-12-28 02:16:11 +0100)

----------------------------------------------------------------
Group splitting does not use “gnus-parameters”

This version of the patch use “gnus-group-find-parameter” to get
parameters from “newsrc” and from “gnus-parameters”.

----------------------------------------------------------------
Daniel Dehennin (1):
      Use `gnus-parameters' in `gnus-group-split-fancy'

 lisp/gnus-mlspl.el | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lisp/gnus-mlspl.el b/lisp/gnus-mlspl.el
index 3947c67..0470e5e 100644
--- a/lisp/gnus-mlspl.el
+++ b/lisp/gnus-mlspl.el
@@ -149,8 +149,8 @@ Calling (gnus-group-split-fancy nil nil \"mail.others\") returns:
   (let* ((newsrc (cdr gnus-newsrc-alist))
 	 split)
     (dolist (info newsrc)
-      (let ((group (gnus-info-group info))
-	    (params (gnus-info-params info)))
+      (let* ((group (gnus-info-group info))
+	     (params (gnus-group-find-parameter group)))
 	;; For all GROUPs that match the specified GROUPS
 	(when (or (not groups)
 		  (and (listp groups)

Footnotes: 
[1]  http://git.baby-gnu.net/gitweb/gitweb.cgi?p=gnus.git;a=tag;h=refs/tags/feature/use-gnus-parameters-in-gnus-group-split-fancy

-- 
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 --]

  reply	other threads:[~2013-12-28  1:17 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 [this message]
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
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=87k3epg4f5.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).