From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: fetching the description from a link string
Date: Tue, 17 Nov 2015 15:58:38 +0100 [thread overview]
Message-ID: <m2egfo3c69.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <87h9kmb7lm.fsf@gmx.us> (rasmus@gmx.us's message of "Mon, 16 Nov 2015 10:45:41 +0100")
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On 2015-11-16 10:45, Rasmus <rasmus@gmx.us> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Hello,
>>
>> I cannot seem to find in org.el a function that will return the
>> description part of a link. I'm probably missing it … Could someone tell
>> me if such a function exists?
>
> org-element-context on a link will give you what you want. It lives in
> org-element, though.
>
> Something like this when point is on a link,
>
> (let ((e (org-element-context)))
> (buffer-substring-no-properties
> (org-element-property :contents-begin e)
> (org-element-property :contents-end e)))
Thank you for the suggestion. I'm already doing something similar:
#+begin_src emacs-lisp
(let ((link (org-store-link nil))
(name (org-element-property :raw-value (org-element-at-point))))
...)
#+end_src
For some reason I was under the impression that org-element might be
overkill for this, but it works well.
Thanks again,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated November 9, 2015, Mauna Loa Obs.): 399.06 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-11-17 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 14:39 fetching the description from a link string Alan Schmitt
2015-11-16 9:45 ` Rasmus
2015-11-17 14:58 ` Alan Schmitt [this message]
2015-11-28 5:21 ` Sacha Chua
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=m2egfo3c69.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).