From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: npostavs@users.sourceforge.net, aaronjensen@gmail.com,
23928@debbugs.gnu.org
Subject: bug#23928: 25.0.95; Performance regression observable with smartparens
Date: Sun, 10 Jul 2016 22:20:29 +0300 [thread overview]
Message-ID: <83d1mle1vm.fsf@gnu.org> (raw)
In-Reply-To: <a179ca78-ca82-78ad-9b7b-e66241c42c7b@yandex.ru> (message from Dmitry Gutov on Sun, 10 Jul 2016 22:17:31 +0300)
> Cc: aaronjensen@gmail.com, npostavs@users.sourceforge.net,
> 23928@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 10 Jul 2016 22:17:31 +0300
>
> I have to say that the idea of using the above for changing the value of
> case-fold-search instead of let, is surprising for me. Most of the time,
> one is using let just for that effect.
It only causes trouble if done in the innermost loops of your
program. Otherwise, the cost is almost negligible.
next prev parent reply other threads:[~2016-07-10 19:20 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
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 [this message]
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=83d1mle1vm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23928@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=dgutov@yandex.ru \
--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.