From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: how to control isearch for invisible text Date: Sat, 12 Aug 2006 15:07:18 -0700 Message-ID: References: <85ejvl4ozu.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1155420479 21591 80.91.229.2 (12 Aug 2006 22:07:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 12 Aug 2006 22:07:59 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 13 00:07:58 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 1GC1e7-0004Nv-HO for ged-emacs-devel@m.gmane.org; Sun, 13 Aug 2006 00:07:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GC1e6-0000ki-SU for ged-emacs-devel@m.gmane.org; Sat, 12 Aug 2006 18:07:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GC1dq-0000fF-OL for emacs-devel@gnu.org; Sat, 12 Aug 2006 18:07:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GC1dp-0000dC-Sx for emacs-devel@gnu.org; Sat, 12 Aug 2006 18:07:38 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GC1dp-0000cn-Gt for emacs-devel@gnu.org; Sat, 12 Aug 2006 18:07:37 -0400 Original-Received: from [148.87.113.118] (helo=rgminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1GC1jH-0004nd-4R for emacs-devel@gnu.org; Sat, 12 Aug 2006 18:13:15 -0400 Original-Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by rgminet01.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id k7CM7ZjE015271 for ; Sat, 12 Aug 2006 16:07:35 -0600 Original-Received: from dradamslap (dhcp-amer-csvpn-gw1-141-144-65-8.vpn.oracle.com [141.144.65.8]) by rgmgw1.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k7CM7YaC026078 for ; Sat, 12 Aug 2006 16:07:34 -0600 Original-To: "Emacs-Devel" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <85ejvl4ozu.fsf@lola.goethe.zz> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE 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:58343 Archived-At: > I have no "actual situation". I was searching through a buffer that > had some invisible text (as an overlay), and I wanted to know if > there was an isearch option for finding it - that's all. You > answered "yes" - thank you. > > I suggested documenting that option better and making it a toggle in > `isearch'. You said it shouldn't be documented better, it shouldn't > be a user option after all, and, a fortiori, it shouldn't be toggled > in `isearch'. What was it that rendered the text invisible in the first place? I used `dired-details-toggle' (a command in library dired-details.el) to hide details in Dired (and, as I said, it uses an overlay). It happened that I wanted to search for something invisible in that context, and I wondered if there was a search option. That's all - there is nothing special about that context. A single keystroke can make everything visible anyway, so there is no special advantage in that context to searching for invisible text. I know search-invisible since preview-latex has to deal with it (actually, it is just the XEmacs port, since the Emacs port works with display properties instead). The mode was responsible for hiding stuff away, and consequently it was also responsible for letting them show up. Since the behavior of isearch needed fixing, I had to check in the source file, anyway. The details were complicated enough that it would have needed quite long and complicated explanations in the Elisp manual, for material that would get checked in the code, anyway. This is my contact with search-invisible. Now could you please explain what mode rendered parts of your text invisible so that one can get an idea whether a global user option makes sense in connection with that? As I said, the context that made me wonder about a possible search option is irrelevant; there is no special need for searching invisible text in that context. It occurred to me that it might be useful, generally, to be able to search invisible text; that's all. > I do hope the user option `search-invisible' 1) remains a user > option, 2) gets better documented, as it seems useful, and 3) gets > an associated toggle in `isearch'. Would you please present an actual example where this would be useful? Sorry, I don't have one, as I already stated in my last message. My crystal ball tells me it will be useful, but my crystal ball has been wrong before too. I like being able to toggle isearch options on the fly, and this is apparently an isearch option (until/unless you kill it). More importantly, I think the option should be documented - perhaps in the section on invisible text, if there is to be no isearch toggle for it. If you want to remove the user option and make it a plain `defvar', that's your choice; I have no actual example that will dissuade you. End of story.