From: Michael Brand <michael.ch.brand@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-elements: list in drawer
Date: Wed, 8 Aug 2012 21:45:40 +0200 [thread overview]
Message-ID: <CALn3zogCSAX_73vjo6OdXki7+UZ8USNYCsfa4rNss+9rh_Qudg@mail.gmail.com> (raw)
In-Reply-To: <878vdpbykt.fsf@gmail.com>
Hi Nicolas
On Wed, Aug 8, 2012 at 10:02 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> I get it now. It should be fixed. Thanks you for the detailed report.
I can confirm, thank you.
>> #+BEGIN_SRC emacs-lisp
>> (plain-list
>> (:type unordered :begin 32 :end 135
>> :contents-begin 32 :contents-end 134 :structure
>> ((32 0 "- " nil nil nil 134))
>> :post-blank 1 :parent
>> (drawer
>> (:begin 21 :end 141 :drawer-name "MYDRAWER" :hiddenp nil
>> :contents-begin 32 :contents-end 135
>> :post-blank 0 :parent nil))))
>> #+END_SRC
>
> The drawer isn't inside the list, it is the value of its `:parent'
> property.
Oh, now I see. It seems that I have to not read over too many of the
“details” of the output of `pp-to-string' (pretty print). Is there a
way to pretty print so that a property value never starts a line and
leaves its property name alone at the end of the previous line?
> Also, `org-element-at-point' doesn't parse contents, so
> there's no reason that there would be the item and the paragraph.
>
> Obviously, `org-element-at-point' output depends on the position of
> point. Try various positions in the same line and you will get,
> consistently, `plain-list', `item' and `paragraph' elements.
Ok, clear. My wrong expectation was that it would return the element
at point including the complete subtree of the structure.
Michael
prev parent reply other threads:[~2012-08-08 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 13:36 org-elements: list in drawer Michael Brand
2012-08-07 7:40 ` Nicolas Goaziou
2012-08-07 19:01 ` Michael Brand
2012-08-08 8:02 ` Nicolas Goaziou
2012-08-08 19:45 ` Michael Brand [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
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=CALn3zogCSAX_73vjo6OdXki7+UZ8USNYCsfa4rNss+9rh_Qudg@mail.gmail.com \
--to=michael.ch.brand@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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 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).