From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: registry seems to be saved for 27.0.50 any longer/Gnorb
Date: Thu, 26 Apr 2018 17:09:32 +0200 [thread overview]
Message-ID: <87po2mj977.fsf@mat.ucm.es> (raw)
In-Reply-To: <87efj2drl6.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
>>> "Michael" == Michael Heerdegen <michael_heerdegen@web.de> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>> Does anybody suffer the same behavior?
> Yes, I had suffered the same.
> The Gnorb registry was horribly broken at that time. It has now
> been fixed, so you need to upgrade. You probably also need to fix
> your Gnus registry. How that can be done should have been posted to
> this Group (or emacs-dev). Or wait until Eric tells more details.
Thanks for confirming! I just realised that Eric indeed send me two
functions, which seem to fix the problem.
I have to call gnus-registry-fixit everytime after I restart gnus, maybe
I should put it in some hook but it is not clear to me into which.
I upgraded (this time successfully to gnorb 1.4.X).
So everything looks ok now, but I think the registry should be fixed
also by Lars/or the GNU emacs maintainers.
Thanks Eric for providing this fix.
Uwe
(defun gnus-registry-strip-quotes (lst)
(let (acc)
(when (consp lst)
(while (eq (car lst) 'quote)
(setq lst (cadr lst)))
(while (consp lst)
(if (eq (car lst) 'quote)
(setq lst (cadr lst))
(push (gnus-registry-strip-quotes (car lst)) acc)
(setq lst (cdr lst)))))
(nconc (nreverse (delete-dups acc))
lst)))
(defun gnus-registry-fixit ()
"Fix Gnus registry after eieio-persistent patches.
For use with Emacs master branch, after installing 0afb43eeb, or
the 26 branch, after daa9e853bd."
(interactive)
(unless (gnus-alive-p)
(gnus))
(when gnus-registry-enabled
(with-slots (tracker data) gnus-registry-db
(maphash
(lambda (track-sym hsh)
(maphash
(lambda (k v)
(setf (gethash k hsh)
(gnus-registry-strip-quotes v)))
hsh))
tracker)
(maphash
(lambda (k v)
(setf (gethash k data) (gnus-registry-strip-quotes v)))
data))))
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2018-04-26 15:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:52 Uwe Brauer
2018-04-26 13:28 ` Michael Heerdegen
2018-04-26 15:09 ` Uwe Brauer [this message]
2018-04-26 15:18 ` Michael Heerdegen
2018-04-26 15:55 ` Uwe Brauer
2018-04-26 16:35 ` [change the default registry names] (was: registry seems to be saved for 27.0.50 any longer/Gnorb) Uwe Brauer
2018-04-26 18:46 ` [change the default registry names] Eric Abrahamsen
2018-04-26 19:19 ` Michael Heerdegen
2018-04-26 19:30 ` Eric Abrahamsen
2018-04-27 9:24 ` Uwe Brauer
2018-04-27 16:59 ` Bob Newell
2018-04-27 18:27 ` Eric Abrahamsen
2018-05-07 8:05 ` Uwe Brauer
2018-05-07 23:43 ` Bob Newell
2018-05-10 8:11 ` Uwe Brauer
2018-05-10 12:38 ` Michael Heerdegen
2018-05-11 17:22 ` Uwe Brauer
2018-05-11 17:28 ` Bob Newell
2018-05-07 8:07 ` [setq does not work] (was: [change the default registry names]) Uwe Brauer
2018-04-26 15:15 ` registry seems to be saved for 27.0.50 any longer/Gnorb Uwe Brauer
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=87po2mj977.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).