Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Problems with gnus-registry
Date: Thu, 07 Feb 2008 18:29:59 +0100	[thread overview]
Message-ID: <v9prv8oeso.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86odasai1l.fsf@lifelogs.com>

On Thu, Feb 07 2008, Ted Zlatanov wrote:

> On Wed, 06 Feb 2008 21:05:26 +0100 Reiner Steib wrote: 
> RS> IMHO, something with "-ignore-"/"-ignored-" would be a better name for
> RS> consistency with many other Gnus variable including
> RS> `nnmail-split-fancy-with-parent-ignore-groups' and
> RS> `nnmail-cache-ignore-groups'.
>
> There's two variables:
[...]
> ;; The Gnus registry's ignored groups
> (gnus-define-group-parameter
>  registry-ignore
>  :type list
>  :function-document
>  "Whether this group should be ignored by the registry."
>  :variable gnus-registry-ignored-groups
[...]
>  "*Groups in which the registry should be turned off."
[...]
> (defcustom gnus-registry-unfollowed-groups '("delayed$" "drafts$" "queue$" "INBOX$")
>   "List of groups that gnus-registry-split-fancy-with-parent won't return.
[...]
> They are used differently.  Ignored groups are not saved in the
> registry, but they are followed for splitting (this is incorrect, I
> think).  Unfollowed groups are not followed by
> gnus-registry-split-fancy-with-parent function but they are saved.
>
> I think the two should be united in one variable, specifically
> gnus-registry-ignored-groups since it's more powerful and should do the
> same thing.

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.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2008-02-07 17:29 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 [this message]
2008-02-08 11:58                             ` David
2008-02-14 17:51                               ` Ted Zlatanov
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=v9prv8oeso.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.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).