Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Registry is working (first cut)
Date: Wed, 30 Apr 2003 12:26:07 -0400	[thread overview]
Message-ID: <4nptn4ar4w.fsf@lockgroove.bwh.harvard.edu> (raw)

I consider this a bug-fixing patch to the registry, since it didn't
work at all well before.  I'll feel better knowing a semi-working
version is going into Gnus 5.10.

If you load gnus-registry.el, the following will happen:

- all messages will be tracked to the group where they are spooled,
  copied, or moved.  Deletions are also caught.  Multiple groups (for
  a copy) are OK, only the latest one is caught.

- when you enter a group, the message IDs of all the articles will be
  registered, UNLESS the article is already registered.  Thus,
  multiple copies will not be registered when you enter a group.

NOTE: I'd like to limit this to mail groups only, what's the
"canonical" way?  message-this-is-{news|mail} didn't seem to work when
I tested it.  In the meanwhile, you will get a lot of registered
messages from newsgroups...

- only the short version of the group name is saved, for many reasons

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

- gnus-registry-split-fancy-with-parent works exactly like
  nnmail-split-fancy-with-parent, just use 

(: gnus-registry-split-fancy-with-parent) 

  in your split-fancy rules.

- gnus-registry-clear can be invoked to clear the registry, if you
  need to.

Have fun with it...

Thanks
Ted



             reply	other threads:[~2003-04-30 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 16:26 Ted Zlatanov [this message]
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   ` Registry is working (first cut) Ted Zlatanov
2003-05-09 17:10     ` 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=4nptn4ar4w.fsf@lockgroove.bwh.harvard.edu \
    --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).