From: Ted Zlatanov <tzz@lifelogs.com>
To: David <de_bb@arcor.de>
Cc: ding@gnus.org
Subject: Re: Problems with gnus-registry
Date: Thu, 14 Feb 2008 11:51:29 -0600 [thread overview]
Message-ID: <86wsp777fi.fsf@lifelogs.com> (raw)
In-Reply-To: <kzve4zfyna.fsf@kafka.physik3.gwdg.de> (David's message of "Fri, 08 Feb 2008 12:58:17 +0100")
On Fri, 08 Feb 2008 12:58:17 +0100 David <de_bb@arcor.de> wrote:
D> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> As we want to store marks (or "labels") in the registry, wouldn't it
>> make sense to have two different variables? (Though both should/could
>> contain "ignore" in the name, like the related nnmail-* variables.) A
>> user might want to ignore some groups for parent splitting, but want
>> to set marks in these groups.
D> I second that, please keep both variables. But I think it should be made
D> clearer that the variable currently named
D> gnus-registry-unfollowed-groups is related to splitting only, so maybe
D> call it gnus-registry-split-with-parent-ignored-groups or something like
D> that.
I'd like to avoid the two variables, see my proposal separately. If you
and Reiner feel strongly they should be separate, though, I'll go along.
D> By the way, I'm currently playing around with the registry labels and
D> was wondering: what would currently be the best way to get all message
D> ids with a certain label? This way, I could easily create nnmairix
D> groups containing only these messages.
Currently there's no reverse mapping. We have it for subject and
sender, and it should be fairly easy to generalize it for multi-value
entries like the labels. See gnus-registry-fetch-extra-entry for the
cache insertion part; gnus-registry-split-fancy-with-parent uses the
cache. I think the code could be much better, BTW.
Ted
next prev parent reply other threads:[~2008-02-14 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 15:21 Jake Colman
2008-02-01 20:57 ` Ted Zlatanov
2008-02-04 13:38 ` Jake Colman
2008-02-04 21:03 ` Ted Zlatanov
[not found] ` <76y7a0nyo3.fsf@dev-d01.ppllc.com>
[not found] ` <86lk60uwwq.fsf@lifelogs.com>
[not found] ` <764pconmz4.fsf@dev-d01.ppllc.com>
2008-02-05 15:15 ` Ted Zlatanov
2008-02-05 21:51 ` Jake Colman
2008-02-05 22:15 ` Ted Zlatanov
2008-02-05 22:24 ` Jake Colman
2008-02-06 14:21 ` Ted Zlatanov
2008-02-06 16:54 ` Jake Colman
2008-02-06 17:31 ` Ted Zlatanov
2008-02-07 15:42 ` Jake Colman
2008-02-06 20:05 ` Reiner Steib
2008-02-07 15:43 ` Ted Zlatanov
2008-02-07 17:29 ` Reiner Steib
2008-02-08 11:58 ` David
2008-02-14 17:51 ` Ted Zlatanov [this message]
2008-02-28 15:01 ` Ted Zlatanov
2008-02-28 15:53 ` David
2008-02-14 17:45 ` Ted Zlatanov
2008-02-28 15:03 ` Ted Zlatanov
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=86wsp777fi.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=de_bb@arcor.de \
--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).