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: Tue, 22 Mar 2005 11:51:12 +0100 Message-ID: References: <200503211349.j2LDnxX12741@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1111493749 21755 80.91.229.2 (22 Mar 2005 12:15:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 22 Mar 2005 12:15:49 +0000 (UTC) Cc: emacs-devel@gnu.org, Drew Adams , miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 22 13:15:48 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DDiIT-0000ue-Fa for ged-emacs-devel@m.gmane.org; Tue, 22 Mar 2005 13:15:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDiZi-0004Ev-Mm for ged-emacs-devel@m.gmane.org; Tue, 22 Mar 2005 07:33:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDhp1-0000dd-7b for emacs-devel@gnu.org; Tue, 22 Mar 2005 06:45:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDhhu-0007si-PR for emacs-devel@gnu.org; Tue, 22 Mar 2005 06:37:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDhTa-0006tI-SW for emacs-devel@gnu.org; Tue, 22 Mar 2005 06:23:13 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DDgyq-0008RE-V4 for emacs-devel@gnu.org; Tue, 22 Mar 2005 05:51:25 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1DDgyq-0001s5-Dw; Tue, 22 Mar 2005 05:51:24 -0500 Original-To: snogglethorpe@gmail.com In-Reply-To: (Miles Bader's message of "Tue, 22 Mar 2005 13:57:52 +0900") 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:34953 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34953 Miles Bader writes: > On Mon, 21 Mar 2005 15:20:34 -0800, Drew Adams wrote: >> In reply to David's point about preview-latex needing to search and find the >> meta-text: I agree that programs need to be able to find meta-text. The >> point is to separate such meta-text from the content - or at least be _able_ >> to separate/distinguish it. In most modes, at least, Info-search should not >> find strings that are in meta-text (if this is not to difficult to fix). > > How about a text/overlay property that says what text to use for > i-searching instead of the underlying text? Then the mode itself > (or whoever added the corresponding display/invisible property) > could make exactly the right decision -- e.g. David would add the > underlying text, David would do no such thing because searches have to end up at the correct corresponding buffer position, not inside of some overlay property. Which is not even possible if I do a search and replace on a string bracketing an overlay boundary. > but info mode could add the text shown by the display property. > > Something like: > > (overlay-put ov 'isearch-text "This is the search text") > (overlay-put ov 'display (some-bit-map)) I think it is a bad idea. What about matches partly in the text, partly out of it? What should get displayed? The underlying basic unit of a buffer is text. If you don't want it manipulated as text, then don't use text in the first place. Of course, this means that we might have to rethink using "x" as a character to carry images, and use something non-printable. Or it might be a good idea to have a property to mark text non-searchable completely for this case. But we should not build a completely separate reality just for searching. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum