From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Info mutilates user overlays.
Date: 01 Oct 2003 13:33:45 -0400 [thread overview]
Message-ID: <jwvvfr8eukm.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <200310011449.h91EnBN28933@raven.dms.auburn.edu>
> this one, related to the same fact. Position registers get treated
> exactly like overlays and hence are unusable. Bookmarks at first seem
> to work, but malfunction. After you save one bookmark, say in
> (emacs)Secondary Selection, then all subsequent bookmarks in different
> Info files get saved under "Secondary Selection". The user believes
These are bugs (or at least misfeatures). Patches welcome.
> In as far as Miles' question is concerned, I am using overlays to
> highlight regions with a non-nil text or overlay property, but I
> sometimes use overlays to highlight all kinds of stuff. I can always
> rehighlight. That is somewhat inconvenient, but less inconvenient
> than the register-bookmark stuff.
How do you highlight? What do you highlight? What for?
> There is one more problem with that overlay repositioning. Maybe it
> applies to *Help* buffers as well. Unreferenced deleted overlays are
> inaccessible (in as far as I know) and hence are garbage, which (I
> would guess) gets garbage collected. But these repositioned overlays,
> even if unreferenced, remain accessible through (overlays-in 1 2),
> hence are not garbage and would (I guess) never get collected. If
> some package spews out a lot of these overlays and fails to delete
> them during updates, as a result of narrowing, can that get a problem?
Of course it can be a problem. Packages are expected to be careful with
such things and if necessary can use the recently mentioned `evaporate'
property to help garbage-collect them. I think overlays should
default to the `evaporate' behavior, but it's probably too late to change
the default now.
Stefan
next prev parent reply other threads:[~2003-10-01 17:33 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 [this message]
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
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=jwvvfr8eukm.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).