unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: victorhge@gmail.com, npostavs@gmail.com, 30823@debbugs.gnu.org
Subject: bug#30823: 25.3; modification-hooks of overlays are not run in some cases
Date: Sun, 19 Aug 2018 17:46:55 +0300	[thread overview]
Message-ID: <834lfqfm74.fsf@gnu.org> (raw)
In-Reply-To: <jwvefev10ki.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Sat, 18 Aug 2018 23:48:02 -0400)

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Noam Postavsky <npostavs@gmail.com>, victorhge@gmail.com,
>         30823@debbugs.gnu.org
> Date: Sat, 18 Aug 2018 23:48:02 -0400
> 
> > Can we turn the table and ask whether it makes sense to delete an
> > overlay from the modification hooks of that same overlay?
> 
> Yes, it very much does make sense: e.g. you want to keep track of
> a "region unmodified" status, so you place an overlay over that region
> with a modification hook that sets a variable to nil to indicate that
> the region was modified, and once that is done there's no point in
> keeping the overlay any more so you can delete it immediately from that
> modification-hook.

I see that I tried too hard to be gentle, and that must have made my
question unclear, because that's not what I was asking.  I was asking
whether we want to support code which does this, because maybe it is
unreasonable to delete an overlay from within its modification hook.





  reply	other threads:[~2018-08-19 14:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15  4:15 bug#30823: 25.3; modification-hooks of overlays are not run in some cases Ren Victor
2018-03-15  6:00 ` Eli Zaretskii
2018-03-15  7:29   ` Ren Victor
2018-03-31 13:51     ` Noam Postavsky
2018-08-17 20:52       ` Noam Postavsky
2018-08-18  6:49         ` Eli Zaretskii
2018-08-19  3:48           ` Stefan Monnier
2018-08-19 14:46             ` Eli Zaretskii [this message]
2018-08-19 15:43               ` Stefan Monnier
2018-08-19 16:13                 ` Eli Zaretskii
2018-08-20  3:02                 ` Richard Stallman
2018-08-20 16:37                   ` Eli Zaretskii
2018-08-19 20:46           ` Stefan Monnier
2018-08-20 16:34             ` Eli Zaretskii
2018-08-23 12:13           ` Noam Postavsky
2018-08-23 13:57             ` Eli Zaretskii
2018-08-31  3:14               ` Noam Postavsky
2018-08-31 14:25                 ` Eli Zaretskii
2018-09-01 16:38                   ` Noam Postavsky
2018-09-11 11:59                     ` Eli Zaretskii
2018-09-13  1:34                       ` Noam Postavsky
2018-09-13 13:43                         ` Eli Zaretskii
2018-09-14 12:03                           ` Noam Postavsky
2018-09-15  9:23                             ` Eli Zaretskii
2018-09-15 14:10                               ` Noam Postavsky

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=834lfqfm74.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30823@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=npostavs@gmail.com \
    --cc=victorhge@gmail.com \
    /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).