From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, emacs-devel@gnu.org
Subject: Re: master c59e878: Inhibit modification hooks when saving eieio-persistent's
Date: Sat, 02 May 2020 11:18:44 -0700 [thread overview]
Message-ID: <87sggiqjy3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <jwvlfmasc0v.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 02 May 2020 09:32:24 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I'm curious what the objection is -- why would we *want* modification
>> hooks to run when writing an eieio object out to file?
>
> Do you know what modification hooks are used for?
No clue! But eieio-persistent is pretty restrictive in its other
read/write processes (removing text properties, etc), so it seemed like
this would be the wrong tool to use for changing how eieio objects are
written.
> I know some uses, but not all. So it's pretty hard to convince myself
> that there really can't be any good reason why someone might want
> those hooks to be run.
>
> More importantly, `inhibit-modification-hooks` is bound here globally,
> so it will affect behavior of Emacs not just in that temp buffer if some
> code happens to modify other buffers during execution of this code.
> That can be *anything* when you debug the code or when you run
> a sufficiently interesting `object-write` method.
Yes, that's definitely a problem. Anyway, sounds like you and Michael
have found an alternate solution.
prev parent reply other threads:[~2020-05-02 18:18 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
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 [this message]
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=87sggiqjy3.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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.