From: Thibault Marin <thibault.marin@gmx.com>
To: emacs-orgmode@gnu.org
Subject: Preserving links when using org-element-interpret-data
Date: Wed, 05 Oct 2016 23:14:30 -0500 [thread overview]
Message-ID: <87vax62jx5.fsf@dell-desktop.WORKGROUP> (raw)
Hi all,
I am trying to use the org-element tools to modify an org file from elisp code
and I was wondering if the `org-element-parse-buffer' /
`org-element-interpret-data' combo should result in the same content as the
original buffer. I am having issues with links where the target and the
description are both =file:= entries.
My original org looks like this:
#+NAME: org-data
#+begin_example
,#+TITLE: test
[[file:a.png][file:a.png]]
#+end_example
The elisp code parses the org file and outputs the result from
`org-element-interpret-data':
#+NAME: org-interpret
#+BEGIN_SRC emacs-lisp :var org-data=org-data :results verbatim
(let (org-tree)
(with-temp-buffer
(insert org-data)
(setq org-tree (org-element-parse-buffer)))
(org-element-interpret-data org-tree))
#+END_SRC
#+RESULTS: org-interpret
: "#+TITLE: test
:
: [[file:a.png][[[file:a.png]]]]
: "
The input link is transformed from
#+begin_example
[[file:a.png][file:a.png]]
#+end_example
to
#+begin_example
[[file:a.png][[[file:a.png]]]]
#+end_example
Are the additional brackets in the description expected? Is there any way to
achieve what I want: I am trying to get org-element-interpret-data to output the
same link syntax as the input (in my real application, I am changing the
filename).
Thanks in advance for the help.
P.S.: Here is my version information:
#+BEGIN_SRC emacs-lisp :results drawer
(concat (emacs-version) "\n"
(replace-regexp-in-string "@.*)" "@ ... )" (org-version nil t)))
#+END_SRC
#+RESULTS:
:RESULTS:
GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.21.5)
of 2016-09-05 on trouble, modified by Debian
Org-mode version 8.3.6 (release_8.3.6-1179-ga9ae0e @ ... )
:END:
next reply other threads:[~2016-10-06 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 4:14 Thibault Marin [this message]
2016-10-09 7:44 ` Preserving links when using org-element-interpret-data Nicolas Goaziou
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=87vax62jx5.fsf@dell-desktop.WORKGROUP \
--to=thibault.marin@gmx.com \
--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).