From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Info mutilates user overlays. Date: Wed, 1 Oct 2003 20:38:31 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20031002003831.GA1410@fencepost> References: <200310010216.h912Ge027788@raven.dms.auburn.edu> <200310011449.h91EnBN28933@raven.dms.auburn.edu> <200310011914.h91JEZU01874@raven.dms.auburn.edu> <200310012111.h91LBBG03258@raven.dms.auburn.edu> <200310012318.h91NIrR04063@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 1065062600 17334 80.91.224.253 (2 Oct 2003 02:43:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 2 Oct 2003 02:43:20 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Oct 02 04:43:18 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 1A4tR0-0002DZ-00 for ; Thu, 02 Oct 2003 04:43:18 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1A4tR0-0004gJ-00 for ; Thu, 02 Oct 2003 04:43:18 +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 1A4tBo-0002cd-Hi for emacs-devel@quimby.gnus.org; Wed, 01 Oct 2003 22:27:36 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1A4tAd-0002Nq-EY for emacs-devel@gnu.org; Wed, 01 Oct 2003 22:26:23 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1A4tA7-0002F9-61 for emacs-devel@gnu.org; Wed, 01 Oct 2003 22:26:22 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1A4rVq-0006OH-KY for emacs-devel@gnu.org; Wed, 01 Oct 2003 20:40:10 -0400 Original-Received: from miles by fencepost.gnu.org with local (Exim 4.24) id 1A4rUF-0000W1-Bx; Wed, 01 Oct 2003 20:38:31 -0400 Original-To: Luc Teirlinck Content-Disposition: inline In-Reply-To: <200310012318.h91NIrR04063@raven.dms.auburn.edu> User-Agent: Mutt/1.3.28i Blat: Foop 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:16848 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16848 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?