Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Problems with gnus-registry
Date: Wed, 06 Feb 2008 11:54:53 -0500	[thread overview]
Message-ID: <76wspic9eq.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <868x1yp3lr.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 06 Feb 2008 08:21:52 -0600")

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> On Tue, 05 Feb 2008 17:24:18 -0500 Jake Colman <colman@ppllc.com>
   TZ> wrote:

   Jake> So with a gcc, when the backend causes the sent article to spool to
   Jake> the gcc-ed folder, the registry will register that article.  This
   Jake> will work for sent emails as well since it is the gcc that will make
   Jake> the registry see it.  Is this all correct?

   TZ> Yes, that's how it's supposed to work.

So after an email with a gcc is sent, should I immediately see an entry in
.gnus.registry.eld (assuming I did a 'save' and flushed it to disk)?  And is
the list ordered with the most recent entries simply appended to the end?  Or
is there some other kind of ordering?

   TZ> Sorry, I gave you the wrong variable name.  This is the right one with
   TZ> the default value:

   TZ> (setq gnus-registry-unfollowed-groups 
   TZ>  '("delayed$" "drafts$" "queue$" "INBOX$"))

Actually, the default value contains only "delayed", "drafts", and "queue".
Not that INBOX is missing and that none have the trailing "$".  Maybe I'm not
using the latest version of the registry?  Could that be the source of some
of my issues?

   TZ> I will write functions to do the above directly through the registry
   TZ> to make debugging easier, but for the time being stick with grep.

A function that indicates which match was actually used (since it can match
on quite a few things) would be helpful too.

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com



  reply	other threads:[~2008-02-06 16:54 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 [this message]
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
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=76wspic9eq.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.com \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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).