From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: gnus-registry issue ?
Date: Wed, 23 Jul 2003 10:46:11 -0400 [thread overview]
Message-ID: <4n3cgxgv2k.fsf@holmes.bwh.harvard.edu> (raw)
In-Reply-To: <plop87lluq87gc.fsf@gnu-rox.org> (Xavier Maillard's message of "Wed, 23 Jul 2003 01:31:15 +0200")
On Wed, 23 Jul 2003, zedek@gnu-rox.org wrote:
> On 21 jui 2003, Ted Zlatanov said:
>> Do M-x toggle-debug-on-error, then open an article that gives you
>> the error. Hit 't' in the article buffer to show all headers,
>> then do
>>
>> M-: (gnus-registry-split-fancy-with-parent)
>>
>> The stack trace will be helpful, if you get one. Also, the
>> contents of your registry file would be useful for debugging.
>
> Dunno if it can help, but it seems it fails for _ALL_ my mails so
> maybe I have done something wrong. Did I ?
>
> How am I supposed to use this module (can you explain in quick and
> simple step howto setup things ?) ?
First of all, do what I asked above so I can see what's failing for
you.
To use the registry you have to do:
(setq gnus-registry-install t)
(require 'gnus-registry)
From that point on, it's automatic. If your gnus-verbose is high you
will see a message every time an article is moved, copied, deleted, or
spooled. I'm not documenting the gnus-registry yet, because it's
likely to change again. I need to use it for tracking spam/ham
registration and that might require changes of the functionality or
the registry file/data format.
Thanks
Ted
next prev parent reply other threads:[~2003-07-23 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 6:08 Xavier Maillard
2003-07-21 15:36 ` Ted Zlatanov
2003-07-22 23:31 ` Xavier Maillard
2003-07-23 14:46 ` Ted Zlatanov [this message]
2003-07-24 6:22 ` Xavier Maillard
2003-07-25 19:16 ` Ted Zlatanov
2003-07-26 7:41 ` Xavier Maillard
2003-07-26 14:31 ` 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=4n3cgxgv2k.fsf@holmes.bwh.harvard.edu \
--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).