From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Gnus registry error after upgrade, using emacs23
Date: Tue, 30 Aug 2011 15:17:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20110830T171058-152@post.gmane.org> (raw)
I just upgraded to today's git Gnus from the Feb 21 version. Using emacs23,
I get the following error when starting Gnus:
Error: Not a lambda list: #[(db)
"\305\b\306\"\x19\307\305\b\310\"\311\b!\305\b\312\"_Z]\x1a\313^[\314\315 \"\210\v\237)\x1c
\f+D\207" [db data limit --cl-var-- candidates eieio-oref :data 0 :max-hard
registry-size :prune-factor nil maphash #[(k --cl-var--) "\b B\211\x11\207" [k
--cl-var--] 2]] 6 "Collects pruning candidates from the registry-db object THIS.
Proposes any entries over the max-hard limit minus size * prune-factor."]
It's in a *Compile-Log* buffer.
If I enable backtraces, I get:
Debugger entered--Lisp error: (void-function registry-reindex)
registry-reindex([object registry-db "Gnus Registry"
"~/Gnus/.gnus.registry.eioio" 0.1 10000 268435455 0.1 (subject sender
recipient mark group keyword) (mark) #<hash-table 'eql nil 0/100 0x8399c58>
#<hash-table 'equal nil 0/10000 0x8aecc40>])
gnus-registry-fixup-registry([object registry-db "Gnus Registry"
"~/Gnus/.gnus.registry.eioio" 0.1 10000 268435455 0.1 (subject sender
recipient mark group keyword) (mark) #<hash-table 'eql nil 0/100 0x8399c58>
#<hash-table 'equal nil 0/10000 0x8aecc40>])
gnus-registry-make-db()
(defvar gnus-registry-db (gnus-registry-make-db)
("/home/jdc/emacs/gnus/lisp/gnus-registry.elc" . -7162))
gnus-registry-initialize()
byte-code(...)
load("~/Gnus/.gnus" nil t)
gnus-read-init-file()
gnus-1(2 t nil)
gnus(2 t)
jdc-gnus-no-server()
[Sorry about the line breaks/control characters. Posting via the gmane web
interface.]
This is using the eieio fallback lib. The one in my version of Ubuntu is
too old.
Any suggestions?
Dan
next reply other threads:[~2011-08-30 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 15:17 Dan Christensen [this message]
2011-09-05 0:33 ` Dan Christensen
2011-09-10 21:34 ` Lars Magne Ingebrigtsen
2011-09-11 5:32 ` Dan Christensen
2011-09-12 4:38 ` Lars Magne Ingebrigtsen
2011-09-13 1:49 ` Dan Christensen
2011-09-13 8:42 ` David Engster
2011-09-13 12:05 ` Dan Christensen
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=loom.20110830T171058-152@post.gmane.org \
--to=jdc@uwo.ca \
--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).