From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus: Thread notes?
Date: Mon, 18 Dec 2017 11:04:09 -0800 [thread overview]
Message-ID: <87zi6fkgd2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r2rs1cy1.fsf@web.de> (Michael Heerdegen's message of "Mon, 18 Dec 2017 12:40:38 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Well that's deeply weird. You have an entry in your registry that
>> looks like:
>>
>> ("" '''''''''''''''''''''''''''''''''''''''''''''''''''''''\
>> ((creation-time (23012 49774 793490 105000)) (group) (sender)
>> (subject)))
>>
>> Ie, no key at all
>
> The empty string is the key, I think.
Yes, in the sense that it's *supposed* to be the key. But not in the
sense that it's the source of the problem -- I just noticed that my
registry is doing the same thing, and I don't have empty-string keys.
>> , and who knows what's going on with all those quotes.
>>
>> Are there many of those, or just one? And are you running an Emacs that
>> includes e1cc2037a918?
>
> Yes.
>
> I did
>
> (maphash (lambda (key value) (message "%S\n\n" (list key value)))
> (oref gnus-registry-db data))
>
> and nearly all entries have a lot of quotes. I starts with entries with
> 81 quotes, and then the number of quotes seems to decrease slowly. The
> last entries printed only have one quote. I guess there is a quote
> added for every save or so.
>
> But I only have one entry with the empty string as key.
>
>> I looked at the code, and there's nothing that would prevent the
>> creation of an entry for a message that had no Message-ID, so presumably
>> the blank there is possible. That doesn't explain all the quotes,
>> though.
>
> Yes, it's horribly broken...
Actually, it's my fault, not the registry's. I patched the persistence
process in e1cc2037a918 so that objects inside hash tables were written
and read correctly. But it looks like the trick I was using writes a
call to `quote' where there shouldn't be one, and those accumulate.
Bummer. I will go back to the other bug thread with this.
Sorry!
Eric
next prev parent reply other threads:[~2017-12-18 19:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 12:44 Gnus: Thread notes? Michael Heerdegen
2017-10-12 12:56 ` Danny YUE
2017-10-12 16:36 ` Göktuğ Kayaalp
2017-10-12 19:25 ` Robert Pluim
2017-10-13 2:21 ` Eric Abrahamsen
2017-10-16 19:33 ` Michael Heerdegen
2017-10-16 20:14 ` Eric Abrahamsen
2017-10-18 12:18 ` Michael Heerdegen
2017-10-18 14:53 ` Eric Abrahamsen
2017-11-25 2:42 ` Michael Heerdegen
2017-11-25 6:35 ` Eric Abrahamsen
2017-11-26 5:30 ` Michael Heerdegen
2017-11-28 2:19 ` Eric Abrahamsen
2017-11-28 6:02 ` Michael Heerdegen
2017-11-28 16:44 ` Eric Abrahamsen
2017-11-29 8:10 ` Michael Heerdegen
2017-11-29 17:43 ` Eric Abrahamsen
2017-12-12 12:26 ` Michael Heerdegen
2017-12-12 17:17 ` Eric Abrahamsen
2017-12-13 12:42 ` Michael Heerdegen
2017-12-13 18:03 ` Eric Abrahamsen
2017-12-14 11:31 ` Michael Heerdegen
2017-12-14 23:41 ` Eric Abrahamsen
2017-12-15 11:38 ` Michael Heerdegen
2017-12-15 17:58 ` Eric Abrahamsen
2017-12-15 19:54 ` Michael Heerdegen
2017-12-16 6:10 ` Eric Abrahamsen
2017-12-28 20:30 ` Eric Abrahamsen
2017-12-14 15:30 ` Michael Heerdegen
2017-12-14 16:05 ` Michael Heerdegen
2017-12-14 16:59 ` Eric Abrahamsen
2017-12-14 17:25 ` Michael Heerdegen
2017-12-14 17:54 ` Eric Abrahamsen
2017-12-16 12:21 ` Michael Heerdegen
2017-12-16 21:08 ` Eric Abrahamsen
2017-12-18 11:40 ` Michael Heerdegen
2017-12-18 19:04 ` Eric Abrahamsen [this message]
2017-12-19 14:27 ` Michael Heerdegen
2017-12-19 16:14 ` Eric Abrahamsen
2017-11-28 7:44 ` Michael Heerdegen
2017-11-26 5:49 ` Michael Heerdegen
2017-10-15 15:43 ` Narendra Joshi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zi6fkgd2.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).