From: Miles Bader <miles@gnu.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Info mutilates user overlays.
Date: Wed, 1 Oct 2003 20:38:31 -0400 [thread overview]
Message-ID: <20031002003831.GA1410@fencepost> (raw)
In-Reply-To: <200310012318.h91NIrR04063@raven.dms.auburn.edu>
On Wed, Oct 01, 2003 at 06:18:53PM -0500, Luc Teirlinck wrote:
> I will take a closer look at it, but at first sight
> `Info-selection-hook' looks like it might work. There probably are
> other *info* style buffers, so I still would have to tell that in
> certain situations manual re-highlighting will be necessary.
I think Stefan's comparison with window-system display updates is apropos.
Perhaps a similar solution would be in order: if there are situations where
it's desirable for overlays (&c) to be re-established after a buffer-smashing
operation, maybe there should just be a list of (FUNCTION . ARGS) entries,
and (apply FUNCTION ARGS) would be done on each entry after such an event.
Are there other places than info where a buffer gets smashed in a way that
doesn't entirely invalidate the data anyway (re-visiting a file comes to
mind)?
-Miles
--
Come now, if we were really planning to harm you, would we be waiting here,
beside the path, in the very darkest part of the forest?
next prev parent reply other threads:[~2003-10-02 0:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 2:16 Info mutilates user overlays Luc Teirlinck
2003-10-01 2:26 ` Miles Bader
2003-10-01 2:40 ` Luc Teirlinck
2003-10-01 4:00 ` Luc Teirlinck
2003-10-01 4:37 ` Miles Bader
2003-10-01 12:22 ` Stefan Monnier
2003-10-01 14:49 ` Luc Teirlinck
2003-10-01 17:33 ` Stefan Monnier
2003-10-01 18:49 ` Luc Teirlinck
2003-10-01 20:00 ` Stefan Monnier
2003-10-02 13:45 ` Richard Stallman
2003-10-01 19:14 ` Luc Teirlinck
2003-10-01 19:54 ` Stefan Monnier
2003-10-01 21:11 ` Luc Teirlinck
2003-10-01 23:18 ` Luc Teirlinck
2003-10-02 0:38 ` Miles Bader [this message]
2003-10-01 15:10 ` Luc Teirlinck
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=20031002003831.GA1410@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).