From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-context at the beginning of a link
Date: Sat, 22 Nov 2014 07:23:32 -0800 [thread overview]
Message-ID: <m2vbm7i7ij.fsf@polytechnique.org> (raw)
In-Reply-To: <87egsw5gee.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 21 Nov 2014 23:37:45 +0100")
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On 2014-11-21 23:37, Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> I'm using a function that relies on `org-element-link-parser'. According
>> to the documentation, the point needs to be at the element of the link
>> for it to work.
>
> Not what you are asking for, but it is probably wrong to call this
> function directly. If you want to parse something, it's better to use
> `org-element-context' (or `org-element-at-point' but it doesn't fit
> here).
Thank you for the suggestion. The reason I was using `org-context' is
because it is used in `org-next-link'.
Here is what I ended up doing. It works great, but please don't hesitate
to criticize is.
#+begin_src emacs-lisp
(defun as/org-link-p (elt)
(eq 'link (org-element-type elt)))
(defun as/fetch-element-link (elt)
(org-element-property :raw-link elt))
(defun as/fetch-current-or-next-link ()
(let ((elt (org-element-context)))
(save-excursion
(as/fetch-element-link
(if (as/org-link-p elt)
elt
(progn (org-next-link) (org-element-context)))))))
#+end_src
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
prev parent reply other threads:[~2014-11-22 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 16:31 org-context at the beginning of a link Alan Schmitt
2014-11-21 22:37 ` Nicolas Goaziou
2014-11-22 15:23 ` Alan Schmitt [this message]
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=m2vbm7i7ij.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).