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:40:52 -0400 [thread overview]
Message-ID: <jwvees3th6b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y2qb9tv3.fsf@web.de> (Michael Heerdegen's message of "Sat, 02 May 2020 00:24:16 +0200")
> I don't want to conceal that I have on-screen.el making use of
> after-change hooks - but I dunno what other people might have put
> there.
Indeed, on-screen.el adds itself *globally* to `after-change-functions`
so it's also applied to temp buffers. Sounds like a performance bug in
`on-screen.el`.
Do you still see the performance problem if you don't enable `on-screen`?
>> Have you tried to use `combine-change-calls`?
> No, but that's something I can try, yes. Actually, `object-write' would
> be the better place to use this,
Not necessarily: it could be too slow (because of the cost to
enter/leave `combine-change-calls`).
Stefan
next prev parent reply other threads:[~2020-05-01 22:40 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
2020-05-01 22:24 ` Michael Heerdegen
2020-05-01 22:40 ` Stefan Monnier [this message]
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
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=jwvees3th6b.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 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).