From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24340@debbugs.gnu.org
Subject: bug#24340: insert-file-contents calls before-change-functions too late
Date: Wed, 31 Aug 2016 10:48:09 -0400 [thread overview]
Message-ID: <jwvtwe1ngk2.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83vayhkogv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 Aug 2016 17:22:24 +0300")
> I'm sorry, but I must insist. The change I proposed is the only one
> in insert-file-contents for that use case that I'm prepared to
> consider in the current situation. (We could also leave this bug
> open, until such time as a more thorough refactoring is done of the
> related functionalities.) Deeper changes are exactly the can of worms
> that I don't want to open to fix just this one use case, especially
> since Emacs 25.2 will almost certainly be branched from what now is
> the master branch. Such deeper changes were what Alan proposed in the
> first place (with a similar patch), and I already said I didn't want
> to do that.
Right: I do not intend for my patch to go to 25.2. But for Emacs-26,
it seems there's plenty of time to find and fix any possible fallout.
> I think a cleaner way is to change the model of how we partition
> piecemeal changes, when we signal the changes and when don't, when we
> ask the user about supersession-threat, etc. The current model is
> fundamentally flawed, if we want to use the buffer-change hooks in the
> ways that emerged from these discussions.
All I care about is for any change to the buffer to be announced by
a prior b-c-f.
Stefan
next prev parent reply other threads:[~2016-08-31 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 18:42 bug#24340: insert-file-contents calls before-change-functions too late Stefan Monnier
2016-08-30 19:10 ` Eli Zaretskii
2016-08-30 21:21 ` Stefan Monnier
2016-08-31 14:22 ` Eli Zaretskii
2016-08-31 14:48 ` Stefan Monnier [this message]
2016-08-31 15:03 ` Eli Zaretskii
2016-08-31 17:50 ` Stefan Monnier
2016-10-02 1:11 ` Stefan Monnier
2016-10-02 7:19 ` Eli Zaretskii
2016-10-03 13:48 ` Stefan Monnier
2016-10-03 14:13 ` 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
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=jwvtwe1ngk2.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=24340@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).