Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Registry is working (first cut)
Date: Thu, 08 May 2003 09:58:38 -0400	[thread overview]
Message-ID: <m3y91hsfox.fsf@heechee.beld.net> (raw)
In-Reply-To: <gd.87znm3od82.fsf@mde1.zonix.de> (Raymond Scholz's message of "Sun, 04 May 2003 00:51:57 +0200")

On Sun, 04 May 2003, ray-2003@zonix.de wrote:
> There is code to avoid registering groups matching "^nntp" in there.
> But the comparison ist made against `gnus-newsgroup-name' which
> doesn't carry this prefix if it is the primary select method.

Yes, it's not a good method.  I think I'll use group parameters, as
suggested by Reiner.

>> - only the short version of the group name is saved, for many
>>   reasons
> 
> I used to have some nnml and nnfolder groups with the same name...

Yes, I would like to use the long names, but I haven't found a
reliable way to capture that.  If anyone can help me obtain the
correct long name for a group, I'm all ears.  I kept getting the wrong
backend on things like drafts, article moves/copies, spooling, etc.

>> - the registry will be saved in your .newsrc.eld.  I can change
>>   that if people feel it's too large.  I optimized the format a
>>   bit, so it should be fast and compact now.
> 
> I think it would be useful to put in a separate file.

I can separate into a file, any suggestions for the name?

I will try to get nnimap storage of files to work, so that you can
store the registry in an article on a nnimap server.  That would be
useful.  I sort of left that project on the side for a little bit, but
it's time to get it working so people don't have to use rsync to
synchronize their registry.

> I wan't to reestablish some sort of "splitting with parent".  This
> is my current setup, which gives me the backtrace below:
> 
> (require 'gnus-registry)
> (setq nnimap-split-fancy
>       '(|
> ;	(: nnmail-split-fancy-with-parent)
> 	(: gnus-registry-split-fancy-with-parent)
> 	"INBOX"))
> 
> (setq nnimap-split-rule 'nnimap-split-fancy)
> (setq nnimap-split-inbox '("INBOX"))
> (setq nnimap-split-predicate "UNDELETED")

I see the problem, it's nnmail-split-fancy-with-parent-ignore-groups,
which can be a single regexp.  I only treated it as a list.  Should be
OK now, I put a change in CVS.

Thanks
Ted




  parent reply	other threads:[~2003-05-08 13:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 16:26 Ted Zlatanov
2003-05-03 22:51 ` Raymond Scholz
2003-05-04 11:01   ` Reiner Steib
2003-05-08 14:05     ` Ted Zlatanov
2003-05-08 16:25       ` Karl Pflästerer
2003-05-08 18:47         ` Modification to newsrc saving, please check! (was: Registry is working (first cut)) Ted Zlatanov
2003-05-09 16:35           ` Modification to newsrc saving, please check! Ted Zlatanov
2003-05-18  9:10           ` Kai Großjohann
2003-05-20 17:37             ` Ted Zlatanov
2003-05-22  7:05               ` Kai Großjohann
2003-05-08 13:58   ` Ted Zlatanov [this message]
2003-05-09 17:10     ` Registry is working (first cut) Ted Zlatanov
2003-05-11 14:01     ` Raymond Scholz
2003-05-11 14:08       ` Raymond Scholz
2003-05-11 18:02       ` Ted Zlatanov
2003-05-12 19:16         ` Ted Zlatanov
2003-05-18  9:11     ` Kai Großjohann

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=m3y91hsfox.fsf@heechee.beld.net \
    --to=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).