emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bug: Can not search for text in links - only description
Date: Tue, 31 Mar 2015 09:46:15 -0400	[thread overview]
Message-ID: <m2k2xxp9eg.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8uv-14H7q6ktviAtE_Rc=mJgLH0d9pOaAe2R6VN+oQXTg@mail.gmail.com>


On 2015-03-20 at 13:53, Samuel Wales <samologist@gmail.com> wrote:
> hmm:
>
> ===
> search-invisible is a variable defined in `isearch.el'.
> Its value is open
>
> Documentation:
> If t incremental search/query-replace can match hidden text.
> A nil value means don't match invisible text.
> When the value is `open', if the text matched is made invisible by
> an overlay having an `invisible' property and that overlay has a property
> `isearch-open-invisible', then incremental search will show the contents.
> (This applies when using `outline.el' and `hideshow.el'.)
> ...
> ===


Note that setting search-invisible to t means that collapsed segments no longer expand.

  -k.
  

  parent reply	other threads:[~2015-03-31 13:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 13:44 Possible bug: Can not search for text in links - only description Rainer M Krug
2015-03-20 14:59 ` Richard Lawrence
2015-03-20 15:20   ` Sebastien Vauban
2015-03-21 23:34   ` Alexis
2015-03-20 15:38 ` Jacob Gerlach
2015-03-20 16:50   ` Ken Mankoff
2015-03-20 18:06     ` Charles C. Berry
2015-03-22  0:08       ` Jacob Gerlach
2015-03-23 12:42       ` Rainer M Krug
2015-03-23 14:37         ` Achim Gratz
2015-03-23 16:56           ` Rainer M Krug
2015-03-23 12:40   ` Rainer M Krug
2015-03-20 17:53 ` Samuel Wales
2015-03-20 17:57   ` Jacob Gerlach
2015-03-31 13:46   ` Ken Mankoff [this message]
2015-03-31 20:07     ` Samuel Wales
2015-03-21 23:45 ` Randomcoder
2015-03-23 12:45 ` Rainer M Krug
2015-03-23 12:57   ` Jacob Gerlach

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.orgmode.org/

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

  git send-email \
    --in-reply-to=m2k2xxp9eg.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /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/org-mode.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).