From: Eike <eike@eknet.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Eike <news@eknet.org>, org-mode <emacs-orgmode@gnu.org>
Subject: Re: org-elements-parse-buffer and weird property drawers
Date: Sun, 31 Aug 2014 14:59:08 +0200 [thread overview]
Message-ID: <87ha0szu5b.fsf@ithaka.home> (raw)
In-Reply-To: <874mwtvvo6.fsf@nicolasgoaziou.fr>
Hello,
Nicolas Goaziou writes:
> Eike <news@eknet.org> writes:
>
>> I'm playing with the functions in org-elements.el and the following
>> effect seems strange to me:
>>
>> I have a few propery drawers with empty propertys, like
>>
>> #+BEGIN_EXAMPLE
>> :PROPERTIES:
>> :date: [2014-08-29 Fr]
>> :chf: 21.76
>> :eur:
>> :END:
>> #+END_EXAMPLE
>>
>> If I do org-elements-parse-buffer, the empty one is not there, but the
>> first one is duplicated. At least, there are two node-property
>> elements in the tree like that:
>>
>> #+BEGIN_EXAMPLE
>> (node-property (:key "chf" :value "21.76" :begin 38 :end 58 :post-blank 0 :post-affiliated 38 :parent #4))
>> (node-property (:key "chf" :value "21.76" :begin 58 :end 67 :post-blank 0 :post-affiliated 58 :parent #4))
>> #+END_EXAMPLE
>>
>> The function call was this:
>>
>> #+begin_src emacs-lisp
>> (with-current-buffer "test-exp.org"
>> (org-element-parse-buffer))
>> #+end_src
>>
>> And here is the "test-exp.org" org file:
>>
>> #+BEGIN_EXAMPLE
>> * Sonstiges
>> ** Pizza
>> :PROPERTIES:
>> :chf: 21.76
>> :eur:
>> :END:
>> #+END_EXAMPLE
>
> This should be fixed. Thank you for reporting it.
Many thanks! It works here now.
Regards,
Eike
next prev parent reply other threads:[~2014-08-31 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 17:56 org-elements-parse-buffer and weird property drawers Eike
2014-08-30 19:02 ` Eike
2014-08-30 19:46 ` Thorsten Jolitz
2014-08-31 9:46 ` Nicolas Goaziou
2014-08-31 12:59 ` Eike [this message]
2014-09-02 9:42 ` Daimrod
2014-09-02 10:35 ` Nicolas Goaziou
2014-09-02 11:14 ` Daimrod
2014-09-02 18:58 ` Will Monroe
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=87ha0szu5b.fsf@ithaka.home \
--to=eike@eknet.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=news@eknet.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).