From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: npostavs@users.sourceforge.net, 23928@debbugs.gnu.org
Subject: bug#23928: 25.0.95; Performance regression observable with smartparens
Date: Sun, 10 Jul 2016 19:14:43 +0300 [thread overview]
Message-ID: <83y459eah8.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48yLCqx4BSnXZnhQF2PRrp0CKxcS_SqiN2DLfNN+kg=vCw@mail.gmail.com> (message from Aaron Jensen on Sun, 10 Jul 2016 15:58:58 +0000)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Sun, 10 Jul 2016 15:58:58 +0000
> Cc: npostavs@users.sourceforge.net, 23928@debbugs.gnu.org
>
> What is the alternative to binding case-fold-search? Could smartparens just bind it once in a surrounding
> function?
That's one way, yes.
> Or is there another way to ensure that `looking-at` is case sensitive?
Does smartparens really care about this? Why?
> When it becomes bad, count the number of buffers in each session.
> Bug#18522 provides some tools for that.
>
> I couldn’t figure out how to count all_buffers, but I saw (length (buffer-list)), is that sufficient?
That's a start, yes.
next prev parent reply other threads:[~2016-07-10 16:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 14:56 bug#23928: 25.0.95; Performance regression observable with smartparens Aaron Jensen
2016-07-09 15:53 ` Noam Postavsky
2016-07-09 17:01 ` Eli Zaretskii
2016-07-10 2:55 ` Aaron Jensen
2016-07-10 14:29 ` Eli Zaretskii
2016-07-10 15:58 ` Aaron Jensen
2016-07-10 16:14 ` Eli Zaretskii [this message]
2016-07-10 16:53 ` Aaron Jensen
2016-07-10 17:14 ` Eli Zaretskii
2016-07-10 18:42 ` Dmitry Gutov
2016-07-10 19:01 ` Eli Zaretskii
2016-07-10 19:17 ` Dmitry Gutov
2016-07-10 19:20 ` Eli Zaretskii
2016-07-10 19:56 ` Dmitry Gutov
2016-07-11 2:28 ` Eli Zaretskii
2016-07-11 2:48 ` Aaron Jensen
2016-07-11 2:49 ` Aaron Jensen
2016-07-11 14:38 ` Eli Zaretskii
2016-07-20 4:58 ` Aaron Jensen
2016-07-20 14:56 ` Eli Zaretskii
2016-07-10 18:49 ` Aaron Jensen
2016-07-09 16:50 ` Eli Zaretskii
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=83y459eah8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23928@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.