From: Adrian Kubala <adrian@sixfingeredman.net>
Subject: gnus-group-split
Date: Fri, 12 Jul 2002 15:44:37 +0200 [thread overview]
Message-ID: <87adoxysai.fsf@sixfingeredman.net> (raw)
I have a very particular split setup, like so:
(setq nnmail-split-methods 'nnmail-split-fancy)
(gnus-group-split-setup t)
(add-hook 'gnus-group-split-updated-hook 'my-fancy-split)
(defun my-fancy-split ()
;; This ugly thing changes the normal & split into an | one
(setq nnmail-split-fancy
(cons '|
(cons '(: nnmail-split-fancy-with-parent)
(append (reverse (cdadr nnmail-split-fancy))
(cddr nnmail-split-fancy))))))
(gnus-group-split-update)
This rather opaque list-manipulation reveals some deficiencies in the
group split.
1. Would it be possible to make the group-split fancy split memoising,
so that `gnus-group-split-update' wasn't necessary? I don't know
elisp too well, perhaps memoising isn't even possible without
lexical binding?
2. The `reverse' is necessary because I like my groups displayed in a
different order than they are sorted. Perhaps topics would be a
partial answer to this. Though it seems a "group-split-priority" in
the group parameters would be really useful.
adrian
reply other threads:[~2002-07-12 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87adoxysai.fsf@sixfingeredman.net \
--to=adrian@sixfingeredman.net \
/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).