Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Problems with gnus-registry
Date: Fri, 18 Jan 2008 10:21:53 -0500	[thread overview]
Message-ID: <76sl0vma5q.fsf@dev-d01.ppllc.com> (raw)


I am starting to use gnus-registry so that emails are filed in the same
folder as its parent.  Unfortunately, it does not seem to be working.
Hopefuly, I am simply just misusing it in some way.

These settings appear in my .gnus file:

-----------------------------------------------

(setq gnus-registry-max-entries 2500
      gnus-registry-use-long-group-names nil)

(gnus-registry-initialize)

(setq nnimap-split-fancy
      '(|
        ; some up-front splitting
        (: gnus-registry-split-fancy-with-parent)

-----------------------------------------------

I will typically send an email such that, using gcc-self, it wil be filed
into a specified group.  I would expect that gnus-registry would auto-file
any reply to that email into the same group as its parent.  Instead, it gets
filed using the other rules contained in nnimap-split-fancy.

Similarly, I will sometimes manually copy an unread email into a specific
group.  I will then go to that group, and reply to that email.  Again
subsequent replies are not filed with its parent.

Finally, incoming emails might be auto-filtered into a specific group via
nnimap-split-fancy.  I will then go to that group, and read and and reply to
that email.  Again subsequent replies are not filed with its parent.

Should gnus-registry handle these cases as I am expecting?  If so, what do I
need to do to make it work?

Any help would be greatly appreciated.

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



             reply	other threads:[~2008-01-18 15:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:21 Jake Colman [this message]
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
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=76sl0vma5q.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.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).