emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [Suggestion] add an API function for getting link description
Date: Thu, 21 May 2020 06:49:39 +0800	[thread overview]
Message-ID: <874ksa8bng.fsf@gmail.com> (raw)
In-Reply-To: <87mu62hfq1.fsf@nicolasgoaziou.fr>

Hash: SHA256

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
> stardiviner <numbchild@gmail.com> writes:
>> I found org link can't get link description easily.
>> I googled it how to get link description. Found this solution. But it's not intuitive.
>> #+begin_src emacs-lisp
>> (defun get-description-at-point ()
>>   (interactive)
>>   (let ((link (org-element-context)))
>>     (message "%s" (buffer-substring (org-element-property :contents-begin link)
>>                                     (org-element-property :contents-end link)))))
>> #+end_src
>> Why now support this?
>> #+begin_src emacs-lisp
>> (org-element-property :desc (org-element-context))
>> #+end_src
>> Maybe the key ~:desc~ could be more meaningful detailed.
> Links with description are not leaf elements in the AST. I.e., the
> parser needs to go deeper. As any non-leaf object, as, e.g., bold, it
> has :contents-begin and :contents-end properties. Adding :desc would
> duplicate information for no good reason.

Hmm, I get the reason. Thanks for explanation.

> I see no problem writing an helper function once, and use it often.
> Besides, there are other, slightly different implementations of this
> function, e.g.,
>   (defun get-description-at-point-2 ()
>     (and (org-at-regexp-p org-link-bracket-re) (match-string 2)))
> This one is fuzzier, it will get description in fake links too (e.g., in
> comments, property drawers…), but will be faster. So there is no single
> function that fits every need.

Good to know another faster implementation. Thankful.


- -- 
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


      reply	other threads:[~2020-05-20 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  9:44 stardiviner
2020-05-20 13:56 ` Nicolas Goaziou
2020-05-20 22:49   ` stardiviner [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:

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


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