From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, yyoncho <yyoncho@gmail.com>
Cc: 39149@debbugs.gnu.org
Subject: bug#39149: 27.0.50; describe-buffer-bindings is calling :filter function in wrong buffer
Date: Sat, 31 Oct 2020 21:31:12 -0700 [thread overview]
Message-ID: <CADwFkm=i6cT9FeP8xh09n9PGki-0=xru06=JQELs_A+Mr2BYEQ@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmNmkpetini5NoLz3Bzv-KfMKdJ-BSDEvBVUjfHkV3Jqw@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
>>> To reproduce (eval in scratch buffer)
>>> (define-key global-map (kbd "C-c C-l r")
>>> `(menu-item "2" switch-to-buffer
>>> :filter ,(lambda (cmd)
>>> (print (format "Called in %s" (current-buffer)))
>>> cmd)))
>>> (with-temp-buffer
>>> (with-output-to-string
>>> (describe-buffer-bindings (get-buffer "*scratch*") [3 12] t)))
>>>
>>> This outputs:
>>>
>>> \"Called in *temp*\"
>>
>> I tried this recipe, but I'm not getting the :filter function called at
>> all. Do you have a recipe, starting from "emacs -Q", that reproduces
>> this bug?
>
> I can reproduce the above on Emacs 26.3, but not on master.
This change in behavior was caused by this commit:
commit 8a1441310aa151e739cfed3bd2eff3358edc8001
Author: Stefan Kangas <stefan@marxist.se>
Date: Sun Oct 18 15:32:22 2020 +0200
Prefer Lisp version of describe-map-tree
So as suspected, there is a difference in behavior between the new Lisp
version of describe-map-tree and the new C version.
next prev parent reply other threads:[~2020-11-01 4:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:59 bug#39149: 27.0.50; describe-buffer-bindings is calling :filter function in wrong buffer yyoncho
2020-10-30 14:23 ` Lars Ingebrigtsen
2020-10-30 16:08 ` yyoncho
2020-10-30 16:16 ` Stefan Kangas
2020-10-30 18:03 ` Basil L. Contovounesios
2020-11-01 14:56 ` Stefan Kangas
2020-11-01 17:01 ` Basil L. Contovounesios
2020-11-01 4:31 ` Stefan Kangas [this message]
2020-11-15 0:24 ` Stefan Kangas
2020-11-15 15:15 ` Eli Zaretskii
2020-11-15 16:08 ` Stefan Kangas
2020-11-15 16:28 ` Eli Zaretskii
2022-04-17 15:37 ` Lars Ingebrigtsen
2022-04-17 16:02 ` Eli Zaretskii
2022-04-17 16:06 ` Lars Ingebrigtsen
2020-10-30 15:16 ` Andreas Schwab
2020-10-30 16:23 ` Stefan Kangas
2020-10-30 16:32 ` yyoncho
2020-10-30 16:46 ` Andreas Schwab
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='CADwFkm=i6cT9FeP8xh09n9PGki-0=xru06=JQELs_A+Mr2BYEQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=39149@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=yyoncho@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).