emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: "Samuel Wales" <samologist@gmail.com>,
	"Pedro R.M. Júnior" <pedrormjunior@gmail.com>
Cc: Emacs Org Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: `org-next-link' skips links inside PROPERTIES drawer
Date: Tue, 21 Jan 2020 03:07:47 +0000	[thread overview]
Message-ID: <878sm15wxo.fsf@kyleam.com> (raw)
In-Reply-To: <CAJcAo8v-wn20CjquZsV4zcxYp2aa=JdSk41fbhBM=f49ACVH7A@mail.gmail.com>

Samuel Wales <samologist@gmail.com> writes:

> is isearch intended to be also affected?  or just org-next-link?  i
> suppose isearch is a generic emacs thing, just as lgrep would be
> generic, and most folk would want it to be generic and would get too
> confused if it were not, but just want to make sure.

No, isearch isn't affected.

> i have noticed a similar issue.  i wonder if it is related to the next
> link issue, or completely different and related to text properties or
> overlays or something?
>
> namely, isearch will not find google in the following link:
>
> [[http://google.com][go]]
>
> is there a hack to make isearch find links?  even though they are
> hidden?

Here are two options:

  * Set search-invisible to t.  (The default value of `open' won't allow
    you to match links.)

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

  reply	other threads:[~2020-01-21  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 22:56 `org-next-link' skips links inside PROPERTIES drawer Pedro R.M. Júnior
2020-01-20 23:31 ` Kyle Meyer
2020-01-21  0:02   ` Pedro R.M. Júnior
2020-01-21  2:19     ` Samuel Wales
2020-01-21  3:07       ` Kyle Meyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-17  0:25 Pedro Ribeiro Mendes Júnior

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=878sm15wxo.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pedrormjunior@gmail.com \
    --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).