Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Problems with gnus-registry
Date: Thu, 14 Feb 2008 11:45:04 -0600	[thread overview]
Message-ID: <861w7f8man.fsf@lifelogs.com> (raw)
In-Reply-To: <v9prv8oeso.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 07 Feb 2008 18:29:59 +0100")

On Thu, 07 Feb 2008 18:29:59 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

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

RS> As we want to store marks (or "labels") in the registry, wouldn't it
RS> make sense to have two different variables?  (Though both
RS> should/could contain "ignore" in the name, like the related nnmail-*
RS> variables.)  A user might want to ignore some groups for parent
RS> splitting, but want to set marks in these groups.

How about naming the single variable gnus-registry-ignored-groups (with
the corresponding topic/group parameter registry-ignore), with values
like this

"nnrss.*" t         ; meaning "ignore"
"nntp.*"  'nofollow ; meaning "do not follow"
"nnml.*"  nil       ; treat normally

It's probably simpler for the users than two separate variables,
especially since "do not follow" a group is a milder form of "ignore
this group."

I think registry labels will not care about this, they don't go by the
group at all, they only use the message ID.  The entry could have no
groups and the labels should still work fine.

Ted



  parent reply	other threads:[~2008-02-14 17:45 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
2008-02-28 15:01                                 ` Ted Zlatanov
2008-02-28 15:53                                   ` David
2008-02-14 17:45                             ` Ted Zlatanov [this message]
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=861w7f8man.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).