From: yyoncho <yyoncho@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 39149@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#39149: 27.0.50; describe-buffer-bindings is calling :filter function in wrong buffer
Date: Fri, 30 Oct 2020 18:32:46 +0200 [thread overview]
Message-ID: <CACCVLQX8mGHdv-rr9G+S9aJpakzyRTJUUC9N39+jRQUO4w2KDA@mail.gmail.com> (raw)
In-Reply-To: <CADwFkm=C_ZTGopkNkrp17Tv_L=KS6wkypL-7xh5g=iWuVe_D7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
Even better will be if there is some intermediate structured result which
can be used by packages like which-key instead of parsing the string.
On Fri, Oct 30, 2020 at 6:23 PM Stefan Kangas <stefankangas@gmail.com>
wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
> > The problem is that describe-buffer-bindings only changes the buffer to
> > look up the bindings, but everything that generates the description
> > (starting with describe-map-tree) doesn't know about that other buffer.
>
> BTW, does anyone know why describe-map and describe-map-tree currently
> inserts its result into buffer instead of just returning a string?
>
[-- Attachment #2: Type: text/html, Size: 1029 bytes --]
next prev parent reply other threads:[~2020-10-30 16:32 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
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 [this message]
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=CACCVLQX8mGHdv-rr9G+S9aJpakzyRTJUUC9N39+jRQUO4w2KDA@mail.gmail.com \
--to=yyoncho@gmail.com \
--cc=39149@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stefankangas@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).