From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: how to control isearch for invisible text Date: Mon, 14 Aug 2006 14:24:45 +0200 Message-ID: <85d5b3tshe.fsf@lola.goethe.zz> References: <854pwh3y55.fsf@lola.goethe.zz> <85d5b3yenv.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1155558328 26622 80.91.229.2 (14 Aug 2006 12:25:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 Aug 2006 12:25:28 +0000 (UTC) Cc: rms@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 14 14:25:26 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GCbVT-0000oq-Qx for ged-emacs-devel@m.gmane.org; Mon, 14 Aug 2006 14:25:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GCbVT-0004rj-2q for ged-emacs-devel@m.gmane.org; Mon, 14 Aug 2006 08:25:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GCbVC-0004pT-3z for emacs-devel@gnu.org; Mon, 14 Aug 2006 08:25:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GCbVB-0004p0-KZ for emacs-devel@gnu.org; Mon, 14 Aug 2006 08:25:05 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GCbVB-0004oj-Ex for emacs-devel@gnu.org; Mon, 14 Aug 2006 08:25:05 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GCbaz-00055n-IY for emacs-devel@gnu.org; Mon, 14 Aug 2006 08:31:05 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1GCbV3-00018r-VE; Mon, 14 Aug 2006 08:24:58 -0400 Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id AFE831C4D3AD; Mon, 14 Aug 2006 14:24:45 +0200 (CEST) Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Mon, 14 Aug 2006 08:14:48 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:58378 Archived-At: Stefan Monnier writes: >>> For reveal-mode, we should just provide a "pre-redisplay-hook" run, >>> as the name indicates, just before doing redisplay. That would >>> allow reveal-mode to do the "show invisible text" even in >>> query-replace and this without even changing query-replace's code. > >> That is a bit heavy-handed for my taste, at least for this purpose. >> Such a hook would have to be global, as redisplay is not a >> buffer-centric activity, and thus every function with a possible need >> would have to register and unregister there, and check the state >> across buffers for every redisplay. > > I doubt it's that hard to implement a proper pre-redisplay-hook which can be > set buffer-locally. This is pretty useless, since in your kind of application, it would be important to know window-point rather than point. The documentation of window-point already states: window-point is a built-in function in `C source code'. (window-point &optional WINDOW) Return current value of point in WINDOW. For a nonselected window, this is the value point would have if that window were selected. Note that, when WINDOW is the selected window and its buffer is also currently selected, the value returned is the same as (point). It would be more strictly correct to return the `top-level' value of point, outside of any save-excursion forms. But that is hard to define. [back] And that is precisely the same problem with reveal-mode: sit-for can be called inside of save-excursions, and the current window-point need not correspond with the point relevant at top-level. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum