unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:50:03 -0400	[thread overview]
Message-ID: <jwvshtkn83v.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83inuhkmkv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 Aug 2016 18:03:12 +0300")

> Since I believe master will be used for 25.2,

[ Making an effort not to comment on that ;-)  ]

> we cannot currently push anything that must wait for 26.

I can wait for this issue to clear up.

>> > 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.
> My proposed simple change satisfies this requirement, albeit the
> effect is less optimal.

Yes, as I said, I prefer my patch, but your suggestion is acceptable
as well.


        Stefan





  reply	other threads:[~2016-08-31 17:50 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
2016-08-31 15:03         ` Eli Zaretskii
2016-08-31 17:50           ` Stefan Monnier [this message]
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=jwvshtkn83v.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).