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: Todays exercise of sanity (or does "see" really match "not"?) Date: Mon, 21 Mar 2005 21:18:42 +0100 Message-ID: References: <002301c52e18$c9b014a0$0200a8c0@sedrcw11488> <200503211349.j2LDnxX12741@raven.dms.auburn.edu> <003401c52e20$d6f79c70$0200a8c0@sedrcw11488> <87hdj4vppf.fsf@jurta.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1111437111 9997 80.91.229.2 (21 Mar 2005 20:31:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 21 Mar 2005 20:31:51 +0000 (UTC) Cc: Lennart Borgman , teirllm@dms.auburn.edu, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 21 21:31:50 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DDTY9-00064V-Pp for ged-emacs-devel@m.gmane.org; Mon, 21 Mar 2005 21:30:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDTpJ-0001O6-8Y for ged-emacs-devel@m.gmane.org; Mon, 21 Mar 2005 15:48:41 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDTlv-0000NG-Um for emacs-devel@gnu.org; Mon, 21 Mar 2005 15:45:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDTlg-0000Hr-UX for emacs-devel@gnu.org; Mon, 21 Mar 2005 15:45:03 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDTlf-0000Cg-0Y for emacs-devel@gnu.org; Mon, 21 Mar 2005 15:44:55 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DDTMU-0007NP-Gn for emacs-devel@gnu.org; Mon, 21 Mar 2005 15:18:54 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1DDTMT-0005ca-G1; Mon, 21 Mar 2005 15:18:54 -0500 Original-To: Juri Linkov In-Reply-To: <87hdj4vppf.fsf@jurta.org> (Juri Linkov's message of "Mon, 21 Mar 2005 21:27:21 +0200") 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34913 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34913 Juri Linkov writes: > "Lennart Borgman" writes: >> From: "Luc Teirlinck" >>> I guess that you have Info-hide-note-references enabled. The reason >>> why it stops on "see" is that the actual text in the buffer is: >>> (*note Character Sets::). and note matches "not". >> >> Thanks. I am feeling better. > > The text "*note " has the `display' text property with the string > "see " which is displayed instead of the original text. The > function `isearch-range-invisible' (which is used by Info search) > doesn't pay attention to the `display' property. It processes only > the `invisible' property. It works the same in all Emacs buffers > with the `display' property (in `image-mode', `w3m' mode, etc.) > where it finds the text not visible on the screen. > > How to handle this situation is not clear. Should isearch find the > displayed text as a contiguous part of the search space? > > The simplest solution is to treat the `display' property like > `invisible' property and to skip the text displayed over the > original text. No, no, no. preview-latex is one such application, and it is essential that the text remains searchable (it will get autoopened if point is inside of it). It's overlays it uses instead of text properties, but that does not change the underlying basics. If we want some text to be impervious to search, you can a) make it a single character, and so point will never be inside b) declare a special property that makes this character not match for searches. But that will also break things like ^.*$, so it would probably be better to use some otherwise unused character and adorn it with proper character class and syntax. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum