From: Noam Postavsky <npostavs@gmail.com>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 31853@debbugs.gnu.org
Subject: bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers
Date: Fri, 15 Jun 2018 22:17:44 -0400 [thread overview]
Message-ID: <87fu1nv5iv.fsf@gmail.com> (raw)
In-Reply-To: <m2k1qzcxse.fsf@gmail.com> (Aaron Jensen's message of "Fri, 15 Jun 2018 18:42:09 -0700")
Aaron Jensen <aaronjensen@gmail.com> writes:
> I don't know how to tell the length of my all_buffers or to see how many
> killed buffers I have.
Try applying Martin's patch from #18522:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18522#198
Then you can do M-: (killed-buffer-names) RET.
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).
next prev parent reply other threads:[~2018-06-16 2:17 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 ` Noam Postavsky [this message]
2018-06-16 6:52 ` bug#31853: 27.0.50; binding case-fold-search is slow when there are many buffers Eli Zaretskii
2018-06-16 13:51 ` Noam Postavsky
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
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=87fu1nv5iv.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31853@debbugs.gnu.org \
--cc=aaronjensen@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).