unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: yoni-r@actcom.com, emacs-devel@gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	rms@gnu.org
Subject: Re: Uninformative comment in files.el
Date: Thu, 13 Dec 2007 20:35:05 +0100	[thread overview]
Message-ID: <85hcimxuae.fsf@lola.goethe.zz> (raw)
In-Reply-To: <47618193.9030909@gmx.at> (martin rudalics's message of "Thu, 13 Dec 2007 20:01:39 +0100")

martin rudalics <rudalics@gmx.at> writes:

>>>I don't think that's true.  Any package that depends on overlays to
>>>correctly survive reverting won't work anyway.  Reverting the buffer
>>>will move the overlay bounds out, at least to cover all the changed
>>>text in the file.  That would break them.
>>
>>
>> Maybe it would.  Or maybe the package knows how to deal with that (it
>> wants the overlay to cover the whole buffer, for instance, and sets the
>> marker's advance-after property appropriately) or it just needs to keep
>> the overlay-buffer info to know in which buffer is the overlay.
>
> We could introduce another overlay property, `keep-when-revert-buffer'
> if removing overlays shall be the default, `remove-when-revert-buffer'
> otherwise.

Well, it may need to be reseated.  So maybe it might be smarter to have
something like a property 'revert-buffer-functions (defaults to
delete-overlay but could be set to nil instead or to other values).  I
am fuzzy about when to call it and with which arguments.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-12-13 19:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 18:46 Uninformative comment in files.el Stefan Monnier
2007-12-11 20:55 ` Vinicius Jose Latorre
2007-12-11 22:05   ` martin rudalics
2007-12-12  2:22     ` Vinicius Jose Latorre
2007-12-12  6:31       ` Yoni Rabkin Katzenell
2007-12-12  9:17         ` martin rudalics
2007-12-12 14:22           ` Yoni Rabkin Katzenell
2007-12-12 12:28         ` Vinicius Jose Latorre
2007-12-12 15:20         ` Stefan Monnier
2007-12-12 15:41           ` Yoni Rabkin Katzenell
2007-12-13 16:51           ` Richard Stallman
2007-12-13 17:00             ` Stefan Monnier
2007-12-13 19:01               ` martin rudalics
2007-12-13 19:35                 ` David Kastrup [this message]
2007-12-14 20:49                   ` Richard Stallman
2007-12-14 20:49               ` Richard Stallman
2007-12-16  3:43                 ` Stephen J. Turnbull
2007-12-17  8:24                   ` Richard Stallman
     [not found]       ` <E1J2aRp-00010Y-QD@fencepost.gnu.org>
     [not found]         ` <476084A9.4010800@ig.com.br>
2007-12-14 10:10           ` Richard Stallman
2007-12-20 23:54             ` Stefan Monnier
2007-12-21 19:49               ` Richard Stallman
2007-12-23  0:57                 ` Stefan Monnier
2007-12-12 22:52   ` Richard Stallman

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=85hcimxuae.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=yoni-r@actcom.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).