From: Samuel Wales <samologist@gmail.com>
To: "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: Mon, 20 Jan 2020 19:19:16 -0700 [thread overview]
Message-ID: <CAJcAo8v-wn20CjquZsV4zcxYp2aa=JdSk41fbhBM=f49ACVH7A@mail.gmail.com> (raw)
In-Reply-To: <m2y2u1oevo.fsf@gmail.com>
thanks from here too! interesting.
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.
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? and find everythign else that isearch does not find, if there
is anythign else?
in 9.1.14, a link like <http://whatever.com> will be found by
org-next-link, so perhaps it is more recent than that.
[now i wodner if whatever kludge i put someplace that makes links in
comments fontified or... clickable... or something... is not needed in
more recent org.]
On 1/20/20, Pedro R.M. Júnior <pedrormjunior@gmail.com> wrote:
> Thanks for the
> clarification and quoted suggestion.
next prev parent reply other threads:[~2020-01-21 2:19 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 [this message]
2020-01-21 3:07 ` Kyle Meyer
-- 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='CAJcAo8v-wn20CjquZsV4zcxYp2aa=JdSk41fbhBM=f49ACVH7A@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).