From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Info mutilates user overlays. Date: 01 Oct 2003 13:33:45 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200310010216.h912Ge027788@raven.dms.auburn.edu> <200310011449.h91EnBN28933@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1065038771 25448 80.91.224.253 (1 Oct 2003 20:06:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 1 Oct 2003 20:06:11 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Oct 01 22:06:09 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A4nEf-0008Lb-00 for ; Wed, 01 Oct 2003 22:06:09 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1A4nEe-0003eX-00 for ; Wed, 01 Oct 2003 22:06:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1A4kt5-0003Zt-Gy for emacs-devel@quimby.gnus.org; Wed, 01 Oct 2003 13:35:43 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1A4krw-0003ZX-Ux for emacs-devel@gnu.org; Wed, 01 Oct 2003 13:34:32 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1A4krO-0003W7-KX for emacs-devel@gnu.org; Wed, 01 Oct 2003 13:34:29 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.24) id 1A4krO-0003Vr-3X for emacs-devel@gnu.org; Wed, 01 Oct 2003 13:33:58 -0400 Original-Received: from vor.iro.umontreal.ca (vor.iro.umontreal.ca [132.204.24.42]) by mercure.iro.umontreal.ca (8.12.9/8.12.9) with ESMTP id h91HXjKS027745; Wed, 1 Oct 2003 13:33:46 -0400 Original-Received: by vor.iro.umontreal.ca (Postfix, from userid 20848) id A17FA3C547; Wed, 1 Oct 2003 13:33:45 -0400 (EDT) Original-To: Luc Teirlinck In-Reply-To: <200310011449.h91EnBN28933@raven.dms.auburn.edu> Original-Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-MailScanner-DIRO: Found to be clean X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16828 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16828 > 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