From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Erik Sjöstrand" <sjostrand.erik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Link descriptions in org-element parser
Date: Mon, 22 May 2017 13:37:30 +0200 [thread overview]
Message-ID: <87y3tpf7gl.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CABHaYhUnZOi-r9ygofWadpnGgKn4iLc87rW9hHvmPfYNZTbQsw@mail.gmail.com> ("Erik Sjöstrand"'s message of "Mon, 22 May 2017 07:51:57 +0000")
Hello,
Erik Sjöstrand <sjostrand.erik@gmail.com> writes:
> I've updated to org-mode 9.0.7 but the problem remains. With this org-mode
> buffer
>
> [[info:emacs#Directory%20variables][info:Directory variables]]
>
> org-element-parse-buffer give the following (indented):
>
> (org-data
> nil
> (section
> (:begin 1 :end 92 :contents-begin 1 :contents-end 92 :post-blank 0
> :post-affiliated 1 :parent #0)
> (paragraph
> (:begin 1 :end 65 :contents-begin 1 :contents-end 64 :post-blank 1
> :post-affiliated 1 :parent #1)
> (link
> (:type info :path emacs#Directory%20variables :format bracket :raw-link
> info:emacs#Directory%20variables :application nil :search-option nil :begin
> 1 :end 63 :contents-begin 37 :contents-end 61 :post-blank 0 :parent #2)
> (link (:type info :path Directory :format plain :raw-link
> info:Directory :application nil :search-option nil :begin 37 :end 52
> :contents-begin nil :contents-end nil :post-blank 1 :parent #3))
> variables))))
>
> So the org-element-contents of the link is another link.
Then it was probably fixed in master branch, i.e., development version.
At least I cannot reproduce it. The fix will be included in Org 9.1.
Regards,
--
Nicolas Goaziou 0x80A93738
prev parent reply other threads:[~2017-05-22 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 21:35 Bug: Link descriptions in org-element parser Erik Sjöstrand
2017-05-21 23:11 ` Nicolas Goaziou
2017-05-22 7:51 ` Erik Sjöstrand
2017-05-22 11:37 ` Nicolas Goaziou [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3tpf7gl.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=sjostrand.erik@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.