emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: stardiviner <numbchild@gmail.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [ISSUE] links navigation not consistent behavior
Date: Wed, 10 Apr 2019 15:34:54 +0200	[thread overview]
Message-ID: <87bm1e56gx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87imvmu76n.fsf@gmail.com> (stardiviner's message of "Wed, 10 Apr 2019 06:48:00 +0800")


stardiviner <numbchild@gmail.com> writes:
> #+begin_src org
> https://www.bing.com
> ,* link in properties drawer
>   :URL:      http://www.google.com
>   :END:
> https://www.bing.com
> ,* http(s) url in content of headline
> https://www.baidu.com
> #+end_src

> In upper example, when I link jumping from first link to next, it will skip the
> url in properties drawer.

This is expected. 

The value in a properties drawer cannot be a link, even though
`org-open-at-point' would normally open it, as is done for comments. 

In addition to no being syntactically a valid link, I think it is
undesirable for an interactive command to display hidden internal data.

If you want to reach it, just write a function calling

   (re-search-forward org-any-link-re nil t)

> When I try to jump backwards, some times reports "no further link found", like
> when I'm on the last link.

I think I fixed this.

Thank you.


Nicolas Goaziou

  reply	other threads:[~2019-04-10 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 23:36 [ISSUE] links navigation not consistent behavior stardiviner
2019-04-02 20:14 ` Nicolas Goaziou
2019-04-03 16:28   ` Nick Dokos
2019-04-04 13:54     ` Nicolas Goaziou
2019-04-08  0:32       ` stardiviner
2019-04-08  9:26         ` Nicolas Goaziou
2019-04-09 22:48           ` stardiviner
2019-04-10 13:34             ` Nicolas Goaziou [this message]
2019-04-11 23:10               ` stardiviner

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:

  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=87bm1e56gx.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    --cc=numbchild@gmail.com \


* 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


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).