From: TSUCHIYA Masatoshi <tsuchiya@namazu.org>
To: ding@gnus.org
Subject: gnus-registry causes an error whenever saving newsrc file
Date: Mon, 18 Feb 2013 22:04:32 +0900 [thread overview]
Message-ID: <87txp9wz6n.fsf@tsuchiya.vaj.namazu.org> (raw)
Hi,
I am using the byte-compiled head version of the master branch of Gnus,
and am using gnus-registry. In these several months, I always see the
following error whenever saving newsrc file.
Debugger entered--Lisp error: (void-function some)
some(#[(entry-key) "..." [entry-key precious] 2] ((subject ...)))
...snip...
registry-prune(...)
...snip...
gnus-registry-save()
run-hooks(gnus-save-newsrc-hook)
apply(run-hooks gnus-save-newsrc-hook)
gnus-run-hooks(gnus-save-newsrc-hook)
gnus-save-newsrc-file(nil)
gnus-group-save-newsrc(nil)
call-interactively(gnus-group-save-newsrc nil nil)
I think that the above error is caused by the fact that `some' is not
declared as an inline function, but cannot find a solution to avoid this
problem. Could you help me?
--
TSUCHIYA Masatoshi
next reply other threads:[~2013-02-18 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 13:04 TSUCHIYA Masatoshi [this message]
2013-02-18 13:33 ` Ted Zlatanov
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=87txp9wz6n.fsf@tsuchiya.vaj.namazu.org \
--to=tsuchiya@namazu.org \
--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).