From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Simplify attributes syntax
Date: Sat, 09 Mar 2013 22:19:05 +0100 [thread overview]
Message-ID: <87hakki852.fsf@gmail.com> (raw)
In-Reply-To: <87hakkcpq2.fsf@gmail.com> (Aaron Ecay's message of "Sat, 09 Mar 2013 14:55:49 -0500")
Hello,
Aaron Ecay <aaronecay@gmail.com> writes:
> I think this patch is a welcome simplification. Would it be possible to
> merge the code that is used for reading babel header args (things like
> “:results output :file foo.txt”) with the code from the exporter?
It is probably possible, but that's way beyond the scope of this patch.
Note that the needs are very different for each reader. Export reader
must be very simple (no escaping character) and only needs to read
strings. OTOH Babel reader has to determine the type of data it reads
(list, number...).
> Unless they are parsed by the same code, the two syntaxes will differ in
> subtle and headache-inducing ways (for users and developers).
It can be troublesome for users in some corner cases (I think Babel
reader uses "none" or "no" where Export reader expects "nil"). I doubt
it will be for developers, who should know which reader they are working
with.
I could replace "nil" -> nil with "no" -> nil in the Export reader, but
I don't like this solution. In English, there are "no", "No", "NO",
"None", "NONE", "none"... but in Elisp, there is only "nil".
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-09 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 0:18 [RFC] Simplify attributes syntax Nicolas Goaziou
2013-03-09 0:44 ` Thomas S. Dye
2013-03-09 13:55 ` Bastien
2013-03-09 14:45 ` Nicolas Goaziou
2013-03-09 19:55 ` Aaron Ecay
2013-03-09 21:19 ` Nicolas Goaziou [this message]
2013-03-11 7:40 ` Nicolas Goaziou
2013-03-13 8:47 ` Christian Egli
2013-03-13 15:28 ` 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=87hakki852.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).