From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: larsi@gnus.org, 39149@debbugs.gnu.org, yyoncho@gmail.com
Subject: bug#39149: 27.0.50; describe-buffer-bindings is calling :filter function in wrong buffer
Date: Sun, 15 Nov 2020 18:28:38 +0200 [thread overview]
Message-ID: <83ima6twi1.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk11-Nez+u5zCS9g5zzsgPqSG2eaU-6jEw7LLm=RHXmeQ@mail.gmail.com> (message from Stefan Kangas on Sun, 15 Nov 2020 08:08:18 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 15 Nov 2020 08:08:18 -0800
> Cc: larsi@gnus.org, yyoncho@gmail.com, 39149@debbugs.gnu.org
>
> > If adding an argument is deemed not a good idea, how about binding a
> > special variable to convey that information to
> > describe-buffer-bindings?
>
> Yes, that could be a third option c). Personally, I like option b)
> better.
If we need to insert stuff into a buffer, why make it a string and
then insert? why not insert directly? The latter means less consing,
so less GC.
next prev parent reply other threads:[~2020-11-15 16:28 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ima6twi1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39149@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.