From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Robert Pluim <rpluim@gmail.com>
Cc: 51796@debbugs.gnu.org
Subject: bug#51796: 29.0.50; gnus-article-describe-key signals (wrong-type-argument listp ..)
Date: Mon, 15 Nov 2021 15:16:14 +0300 [thread overview]
Message-ID: <m2bl2lwr5d.fsf@fastmail.fm> (raw)
In-Reply-To: <87czn4crrw.fsf@gmail.com> (Robert Pluim's message of "Sat, 13 Nov 2021 10:46:11 +0100")
On 13/11/2021 10:46 +0100, Robert Pluim wrote:
>>>>>> On Sat, 13 Nov 2021 00:42:42 +0300, Filipp Gunbin <fgunbin@fastmail.fm> said:
>
> Filipp> Not sure how to give emacs -Q recipe, because Gnus will read .gnus.el
> Filipp> even then?
>
> HOME=/tmp emacs -Q
Thanks!
> Filipp> Anyway, if I:
> Filipp> - go to any Gnus Article buffer
> Filipp> - type "C-h k" (gnus-article-describe-key), then type any key, like "g"
>
> Filipp> I get this error (with debug-on-error turned on):
>
> Filipp> Debugger entered--Lisp error: (wrong-type-argument listp [103])
> Filipp> mapcar(#f(compiled-function (kr) #<bytecode -0x10b5d8d159a06a93>) ("g" . [103]))
> Filipp> describe-key(("g" . [103]) #<buffer *Summary nnfolder+mailserver:ml.emacs-devel*>)
> Filipp> gnus-article-describe-key("g")
> Filipp> funcall-interactively(gnus-article-describe-key "g")
> Filipp> call-interactively(gnus-article-describe-key nil nil)
> Filipp> command-execute(gnus-article-describe-key)
>
> Filipp> I tried make bootstrap, it didn't help.
>
I see Lars already fixed this, but FTR,
> Is your .gnus.el byte-compiled?
No, why would I byte-compile it?
> Is 'gnus-use-byte-compile' t?
Yes, by default.
Filipp
next prev parent reply other threads:[~2021-11-15 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 21:42 bug#51796: 29.0.50; gnus-article-describe-key signals (wrong-type-argument listp ..) Filipp Gunbin
2021-11-13 9:46 ` Robert Pluim
2021-11-15 12:16 ` Filipp Gunbin [this message]
2021-11-15 13:01 ` Robert Pluim
2021-11-14 1:46 ` Lars Ingebrigtsen
2021-11-14 17:35 ` Juri Linkov
2021-11-14 17:47 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2bl2lwr5d.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=51796@debbugs.gnu.org \
--cc=rpluim@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).