emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: "Pedro R.M. Júnior" <pedrormjunior@gmail.com>,
	"Emacs Org Mode mailing list" <emacs-orgmode@gnu.org>
Subject: isearch misses stuff (was: `org-next-link' skips links inside PROPERTIES drawer)
Date: Tue, 21 Jan 2020 12:35:50 -0700	[thread overview]
Message-ID: <CAJcAo8uep7e3OKL5ey=_oZ4Bt9uZGWjcHFGK-6FSB9ay-Rqw_Q@mail.gmail.com> (raw)

hi,

On 1/20/20, Kyle Meyer <kyle@kyleam.com> wrote:
>> is isearch intended to be also affected?  or just org-next-link?  i
>
> No, isearch isn't affected.

thanks, that's a relief.  then we have a "your life in plain text"
(i.e. matches everything) search inside emacs that will also work with
multi-buffer isearch etc.

> Here are two options:
>
>   * Set search-invisible to t.  (The default value of `open' won't allow
>     you to match links.)

i tried t, and it stopped at links without opening them.  i'd prefer
it open them, but it is good that it matched them.

however, it made org entries not open during isearch.  so i don't
think this will work.

the docstring says you can make things open by adding an overlay
property.  i'm not sure what those are.  could this possibly allow
isearch to find links while still opening org entries?

>   * Make the links visible with org-toggle-link-display before
>     searching.

i don't think i would remember to do this, so i would have to
defadvice isearch to do this before searching an org buffer, and then
turn it off after, or something like that?  if i got it to work, i'd
wonder if it would work with multi-isearch.

                 reply	other threads:[~2020-01-21 19:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJcAo8uep7e3OKL5ey=_oZ4Bt9uZGWjcHFGK-6FSB9ay-Rqw_Q@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=pedrormjunior@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).