Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-registry causes an error whenever saving newsrc file
Date: Mon, 18 Feb 2013 08:33:28 -0500	[thread overview]
Message-ID: <8738wt7nmf.fsf@lifelogs.com> (raw)
In-Reply-To: <87txp9wz6n.fsf@tsuchiya.vaj.namazu.org> (TSUCHIYA Masatoshi's message of "Mon, 18 Feb 2013 22:04:32 +0900")

On Mon, 18 Feb 2013 22:04:32 +0900 TSUCHIYA Masatoshi <tsuchiya@namazu.org> wrote: 

TM> I am using the byte-compiled head version of the master branch of Gnus,
TM> and am using gnus-registry.  In these several months, I always see the
TM> following error whenever saving newsrc file.

TM> Debugger entered--Lisp error: (void-function some)
TM>   some(#[(entry-key) "..." [entry-key precious] 2] ((subject ...)))
TM>   ...snip...
TM>   registry-prune(...)
TM>   ...snip...
TM>   gnus-registry-save()
TM>   run-hooks(gnus-save-newsrc-hook)
TM>   apply(run-hooks gnus-save-newsrc-hook)
TM>   gnus-run-hooks(gnus-save-newsrc-hook)
TM>   gnus-save-newsrc-file(nil)
TM>   gnus-group-save-newsrc(nil)
TM>   call-interactively(gnus-group-save-newsrc nil nil)

TM> I think that the above error is caused by the fact that `some' is not
TM> declared as an inline function, but cannot find a solution to avoid this
TM> problem.  Could you help me?

I have not seen this error.  It seems to be related to Emacs' move to
use `cl-' as the prefix of these functions, but `cl.el' should define
the `some' alias to `cl-some'.  Could you check?  `cl.el' is required by
`gnus-registry.el':

#+begin_src lisp
(eval-when-compile (require 'cl))
#+end_src

so this seems like maybe you have an older `cl.el' in your load path?

I am using a dev version of Emacs compiled last week and the registry
works for me.

Ted



      reply	other threads:[~2013-02-18 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 13:04 TSUCHIYA Masatoshi
2013-02-18 13:33 ` Ted Zlatanov [this message]

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=8738wt7nmf.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).