unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: how to control isearch for invisible text
Date: Sat, 12 Aug 2006 19:16:44 +0200	[thread overview]
Message-ID: <85slk16fib.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMGEHFCKAA.drew.adams@oracle.com> (Drew Adams's message of "Sat, 12 Aug 2006 10:09:44 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

>     > It seems like there should be some way to control whether
>     > isearch matches text that is invisible or ignores it.
>
>     > If there is no option..., then how about adding one?
>     > And adding an isearch keymap binding for toggling the
>     > option while searching.
>
>     > It would be a plus if the same option could act
>     > similarly for query-replace and occur. For query-replace,
>     > perhaps the same toggle binding could be used.
>
>     M-x apropos-documentation RET isearch.*invisible RET
>
> Thanks.
>
> So, now, how about:
>
> - documenting `isearch-invisible' in the Emacs manual?

It is `search-invisible'.  I consider it far too special to be
documented in the Emacs manual: this is a variable that should, if at
all, be used by the modes or packages making stuff invisible.

> - and the Elisp manual?

Not sure whether it is important enough for that.

> - creating a toggle for it?

Why?  It is not a user-level feature.  Providing a toggle would be the
task of any mode that makes stuff invisible and that would require to
have it accessible.

> - having `occur' and `query-replace' respect the option?

Sounds sort of reasonable, at least with query-replace.  With occur, I
am less sure, since it is sort of an internal grep.  But since occur
could not reasonably display something useful without making it
visible, it might be an idea.

> Also, I'm curious why the treatment of an `invisible' text-property
> value of `isearch-open-invisible' is limited to overlays. Why
> shouldn't the same behavior hold for the property if applied
> directly to text (that is, without an overlay)?

Because you can make some text visible without modification when there
is an invisible overlay over it.  If there are invisible text
properties, you can't remove them without changing the buffer, and
searching should not change the buffer.

Fiddling with invisibility-spec would affect all invisible regions,
not just the one at point.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-08-12 17:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12  8:30 how to control isearch for invisible text Drew Adams
2006-08-12  8:49 ` David Kastrup
2006-08-12 17:09   ` Drew Adams
2006-08-12 17:16     ` David Kastrup [this message]
2006-08-12 17:56       ` Drew Adams
2006-08-12 19:21         ` David Kastrup
2006-08-12 20:54           ` Drew Adams
2006-08-12 21:02             ` David Kastrup
2006-08-12 21:17               ` Drew Adams
2006-08-12 21:34                 ` David Kastrup
2006-08-12 22:07                   ` Drew Adams
2006-08-12 22:27                     ` David Kastrup
2006-08-12 23:02                       ` Drew Adams
2006-08-13  0:28     ` Stefan Monnier
2006-08-13  7:14       ` David Kastrup
2006-08-13 17:52         ` Richard Stallman
2006-08-13 18:00           ` David Kastrup
2006-08-14  0:36           ` Stefan Monnier
2006-08-14  7:12             ` David Kastrup
2006-08-14 12:14               ` Stefan Monnier
2006-08-14 12:24                 ` David Kastrup
2006-08-14 12:59                   ` Stefan Monnier
2006-08-14 13:48                     ` David Kastrup
2006-08-14 14:43                       ` Stefan Monnier
2006-08-14 15:05                         ` David Kastrup
2006-08-14 15:23                           ` Drew Adams
2006-08-14 15:32                             ` David Kastrup
2006-08-15 12:41                             ` Richard Stallman
2006-08-15 12:40             ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85slk16fib.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).