Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Gnus registry error after upgrade, using emacs23
Date: Mon, 12 Sep 2011 21:49:37 -0400	[thread overview]
Message-ID: <87obypky8e.fsf@uwo.ca> (raw)
In-Reply-To: <m3vcsy9xye.fsf@stories.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> That's right.  In registry.el, it's defined using defmethod, which is
>> something from eieio.el, so maybe the version of eieio.el shipped with
>> gnus is too old?
>
> I'm unable to reproduce this with Emacs 23.  Are you sure you don't have
> bits of older versions of registry/Gnus loaded?

I don't think so.  I checked `M-x list-load-path-shadows' and only found
the expected things, e.g. that the git gnus in my home directory shadows
files from emacs 23.2, and that gnus-fallback-lib/eieio/* shadows files
from emacs 23.2.

I just did another test.  I created a new user, started emacs with
"emacs -q --no-site-file" and then evaluated each of these lines
in the *scratch* buffer:

  (add-to-list 'load-path "/tmp/emacs/gnus/lisp")
  (add-to-list 'load-path "/tmp/emacs/gnus/lisp/gnus-fallback-lib/eieio/")
  (require 'registry)

where /tmp/emacs/gnus is a copy of git gnus as of a couple of weeks ago.
When I evaluated the last one, I got a *Compile-Log* buffer containing:

  Error: Not a lambda list: #[(db) "[lots of 8-bit things deleted]" 
  [db data limit --cl-var-- candidates eieio-oref :data 0 :max-hard
  registry-size :prune-factor nil maphash #[(k --cl-var--) "[more deleted]" 
  [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."]

Here are the eieio files I have:

-rw-rw-r-- 1 jdc jdc  12617 2011-02-21 09:38 eieio-base.el
-rw-rw-r-- 1 jdc jdc   5113 2011-08-30 10:38 eieio-comp.el
-rw-rw-r-- 1 jdc jdc  15808 2011-08-30 10:38 eieio-custom.el
-rw-rw-r-- 1 jdc jdc   4862 2011-02-21 09:38 eieio-datadebug.el
-rw-rw-r-- 1 jdc jdc 117129 2011-08-30 10:38 eieio.el
-rw-rw-r-- 1 jdc jdc  21950 2011-08-30 10:38 eieio-opt.el
-rw-rw-r-- 1 jdc jdc  15789 2011-02-21 09:38 eieio-speedbar.el

And registry.el:

-rw-rw-r-- 1 jdc jdc 18702 2011-08-30 10:38 registry.el

And I'm using

  emacs23 23.2+1-4ubuntu1~ppa3

from 

  https://launchpad.net/~ubuntu-elisp/+archive/ppa

Any ideas?

Dan




  reply	other threads:[~2011-09-13  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 15:17 Dan Christensen
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 [this message]
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=87obypky8e.fsf@uwo.ca \
    --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).