From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31853@debbugs.gnu.org, aaronjensen@gmail.com
Subject: bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers
Date: Sat, 16 Jun 2018 09:51:57 -0400 [thread overview]
Message-ID: <87a7ruvnya.fsf@gmail.com> (raw)
In-Reply-To: <83efh71auu.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Jun 2018 09:52:57 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Although my understanding of the resolution of Bug#18522 is that dead
>> buffers should no longer affect the time for let-binding variables, just
>> live ones (but maybe the fix missed something).
>
> Which fix is that? I think I'm missing it, because I don't think that
> bug resolved the general problem. Maybe I'm forgetting something.
Oh, nevermind, I had gathered from reading the bug#18522 thread that
set-internal's FOR_EACH_BUFFER was replaced with FOR_EACH_LIVE_BUFFER,
but actually looking at the code I see it isn't so.
next prev parent reply other threads:[~2018-06-16 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 1:42 bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Aaron Jensen
2018-06-16 2:10 ` bug#31853: (27.0.50; binding case-fold-search is slow when there are many buffers) Aaron Jensen
2018-06-16 6:51 ` bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Eli Zaretskii
2018-06-30 13:18 ` bug#31853: (27.0.50; binding case-fold-search is slow when there are many buffers) Stefan Monnier
2018-06-30 13:53 ` Eli Zaretskii
2018-06-16 2:17 ` bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Noam Postavsky
2018-06-16 6:52 ` Eli Zaretskii
2018-06-16 13:51 ` Noam Postavsky [this message]
2018-06-16 6:45 ` Eli Zaretskii
2018-06-16 7:39 ` Aaron Jensen
2018-06-16 7:53 ` Eli Zaretskii
2018-06-16 14:54 ` Aaron Jensen
2018-06-17 12:37 ` Aaron Jensen
2018-06-17 13:11 ` Eli Zaretskii
2018-06-23 5:23 ` Aaron Jensen
2018-06-23 6:54 ` Eli Zaretskii
2018-06-30 8:19 ` Eli Zaretskii
2018-06-30 18:22 ` Aaron Jensen
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=87a7ruvnya.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31853@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=eliz@gnu.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.
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.