From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: links are not parsed in keyword context
Date: Mon, 13 Apr 2020 10:27:34 +0200 [thread overview]
Message-ID: <87r1wr23k9.fsf@polytechnique.org> (raw)
Hello,
If you consider the following line in an org file
#+begin_src org
#+FOO: http://alan.petitepomme.net/
#+end_src
then calling ~org-element-context~ returns
#+begin_src emacs-lisp
(keyword
(:key "FOO"
:value "http://alan.petitepomme.net/"
:begin 1
:end 38
:post-blank 1
:post-affiliated 1
:parent nil))
#+end_src
If the same link is in the body of the org file, one gets
#+begin_src emacs-lisp
(link
(:type "http"
:path "//alan.petitepomme.net/"
:format plain
:raw-link "http://alan.petitepomme.net/"
:application nil
:search-option nil
:begin 38
:end 66
:contents-begin nil
:contents-end nil
:post-blank 0
:parent (paragraph
(:begin 38
:end 68
:contents-begin 38
:contents-end 67
:post-blank 1
:post-affiliated 38
:parent nil))))
#+end_src
The link can still be opened in both cases using ~org-open-at-point~,
but it is a problem for org-ref that relies on the second format to
extract the link information (see
https://github.com/jkitchin/org-ref/blob/master/org-ref-core.el#L2045,
where the link is set to ~nil~ because there is no ~:path~ property).
I see that orgmode uses a workaround in ~org-return~ when
~org-return-follows-link~ is set to true, to detect if there is a link
using a regexp
(https://code.orgmode.org/bzg/org-mode/src/maint/lisp/org.el#L18106):
#+begin_src emacs-link
((and org-return-follows-link
(or (org-in-regexp org-ts-regexp-both nil t)
(org-in-regexp org-tsr-regexp-both nil t)
(org-in-regexp org-any-link-re nil t)))
(call-interactively #'org-open-at-point))
#+end_src
Could is be possible to parse a link in keyword context? Alternatively,
should I suggest org-ref uses an approach similar to the one in ~org-return~?
Thanks,
Alan
next reply other threads:[~2020-04-13 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 8:27 Alan Schmitt [this message]
2020-04-13 9:19 ` links are not parsed in keyword context Nicolas Goaziou
2020-04-13 12:59 ` Alan Schmitt
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=87r1wr23k9.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
/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).