From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: master c59e878: Inhibit modification hooks when saving eieio-persistent's
Date: Fri, 01 May 2020 18:03:05 -0400 [thread overview]
Message-ID: <jwvk11vtizq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87368jba7f.fsf@web.de> (Michael Heerdegen's message of "Fri, 01 May 2020 23:45:56 +0200")
> I thought this would be obvious? The output always goes into a fresh
> temp buffer the user never sees, and the goal is to speed things up.
It's far from the only code which adds things to a temp buffer, yet we
usually don't bind that var around such code because the speed
difference is usually not significant.
What kind of speed up have you noticed?
Have you profiled it to see which change-functions slow us down (maybe
we can disable them some other way, such as by using another major mode)?
Have you tried to use `combine-change-calls`?
Stefan
next prev parent reply other threads:[~2020-05-01 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200501192115.23847.67499@vcs0.savannah.gnu.org>
[not found] ` <20200501192116.A55EE20B5B@vcs0.savannah.gnu.org>
2020-05-01 21:01 ` master c59e878: Inhibit modification hooks when saving eieio-persistent's Stefan Monnier
2020-05-01 21:45 ` Michael Heerdegen
2020-05-01 22:03 ` Stefan Monnier [this message]
2020-05-01 22:24 ` Michael Heerdegen
2020-05-01 22:40 ` Stefan Monnier
2020-05-01 23:30 ` Michael Heerdegen
2020-05-02 13:26 ` Stefan Monnier
2020-05-02 21:08 ` Michael Heerdegen
2020-05-02 22:09 ` Stefan Monnier
2020-05-03 2:44 ` Michael Heerdegen
2020-05-03 4:01 ` Stefan Monnier
2020-05-03 5:13 ` Michael Heerdegen
2020-05-04 21:09 ` Eric Abrahamsen
2020-05-04 21:36 ` Michael Heerdegen
2020-05-04 21:42 ` Eric Abrahamsen
2020-05-02 4:24 ` Michael Heerdegen
2020-05-02 0:03 ` Eric Abrahamsen
2020-05-02 0:22 ` Michael Heerdegen
2020-05-02 13:32 ` Stefan Monnier
2020-05-02 18:18 ` Eric Abrahamsen
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=jwvk11vtizq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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.