emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] [PATCH] [parser] org-element.el: Handle block parameters
Date: Thu, 31 Oct 2013 20:08:48 +0100	[thread overview]
Message-ID: <8738nh1cn3.fsf@gmail.com> (raw)
In-Reply-To: <87iowdb92a.fsf@gmail.com> (Aaron Ecay's message of "Thu, 31 Oct 2013 14:15:57 -0400")

Hello,

Aaron Ecay <aaronecay@gmail.com> writes:

> Very interesting.  I did not realize that #+header: could apply to
> elements other than babel blocks.  (Babel blocks are all that is
> documented in the manual, for example.)  But a quick experiment shows
> that they can.  I think #+header with a plist can accomplish all of what
> I wanted.

HEADER is not parsed as a plist but as a list of strings (one per
keyword). Internally, Babel parses it differently (as an alist).

> So, if this is a reliable component of org syntax, I will focus on
> documenting it in the manual.

What feature do you want to document? At the moment, HEADER keywords are
only used on src blocks, by Babel, and this is already documented.

> If you like, I will also remove the references to block parameters on
> worg (or you can do it if you’d rather, since I think you originally
> wrote the syntax document).

Please go ahead. Thank you.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2013-10-31 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 19:04 [RFC] [PATCH] [parser] org-element.el: Handle block parameters Aaron Ecay
2013-10-29  8:20 ` Nicolas Goaziou
2013-10-30  4:28   ` Aaron Ecay
2013-10-30  8:01     ` Nicolas Goaziou
2013-10-30 22:23       ` Aaron Ecay
2013-10-31 11:00         ` Nicolas Goaziou
2013-10-31 18:15           ` Aaron Ecay
2013-10-31 19:08             ` 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

  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=8738nh1cn3.fsf@gmail.com \
    --to=n.goaziou@gmail.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).