"Christopher M. Miles" <[email protected]> writes: > #+begin_src emacs-lisp > (link (:standard-properties [656165 nil 656186 656211 656213 0 nil nil nil > nil nil nil nil nil nil nil nil nil] > :type "file" > :type-explicit-p t > :path "contacts.vcf" > :format bracket > :raw-link "file:contacts.vcf" > :application nil > :search-option nil)) > #+end_src > > We can see `:type`, `:path`, `:raw-link`, etc, except `:description`. As > an Org element API function, it should work as a normal user intuitive > expecting. This function return every parts of link except the > `:description`. Really weird.
I disagree. The concept of "contents" is a part of org-element API as well. It is universally applicable to all the AST elements. We may make something like org-element-link-description an alias to org-element-contents, but that seems excessive. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
