From: Bastien <bzg@altern.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: gnus-registry.el problem (was: tags, keywords, annotations)
Date: Fri, 18 Jan 2008 00:32:57 +0000 [thread overview]
Message-ID: <87prw0ezwm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m2fxwwleo9.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 17 Jan 2008 08:17:26 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> You can move ~/.gnus.registry.eld away for now and call
>
> M-: (gnus-registry-cache-read)
Done. But the error is still here.
,----
| gnus-registry-save: Wrong type argument: characterp,
| ("<DJEGIGMOHCNJDGCAKOICAELNCEAA.domiguerry@free.fr>" ((mtime 18319 62087
| 746294)) "nnml:mail.famille")
`----
> Can you compress and send me your registry file (above)? If you can
> reduce it to just the entries that cause the problem that's even
> better, but you don't have to. I tested with mine yesterday and
> didn't get this error.
I'm not sure it will be useful to send you my .gnus.registry.eld since
it looks like it happens for every new mail I have...
My gnus-registry setup is just this:
,----
| (require 'gnus-registry)
| (setq gnus-registry-max-entries 10000
| gnus-registry-use-long-group-names t
| spam-log-to-registry t)
| (gnus-registry-initialize)
`----
And I use (: gnus-registry-split-fancy-with-parent) in my
`nnmail-split-fancy' variable.
Any other idea is very welcome, since this problem is quite
annoying...
--
Bastien
next prev parent reply other threads:[~2008-01-18 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m0r6gujtpi.fsf@gmail.com>
[not found] ` <mailman.5812.1199695477.18990.info-gnus-english@gnu.org>
[not found] ` <86myrhr2jc.fsf@lifelogs.com>
2008-01-17 13:40 ` tags, keywords, annotations Bastien
2008-01-17 14:17 ` Ted Zlatanov
2008-01-18 0:32 ` Bastien [this message]
2008-01-18 5:02 ` gnus-registry.el problem Ted Zlatanov
2008-01-18 14:22 ` Bastien
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=87prw0ezwm.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).