From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [RFC] [PATCH] [babel] read description lists as lists of lists
Date: Mon, 29 Sep 2014 00:09:12 +0200 [thread overview]
Message-ID: <8761g7wg6v.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87tx3sl254.fsf@gmail.com> (Aaron Ecay's message of "Sun, 28 Sep 2014 01:55:51 -0400")
Aaron Ecay <aaronecay@gmail.com> writes:
> Let’s back up a step. The representation I am targeting with my change
> is what babel uses to ship a list off as input to code in a babel block.
> This code could be emacs lisp, but it could also be R, python, etc. So
> the question is, how to provide a consistent language-agnostic view of
> org structure to other languages. The resultant structure doesn’t hang
> around inside babel, it just gets handed off to a code block.
I know. But another internal representation is an additional maintenance
burden.
> It’s not work that I’m afraid of: I offered to rewrite both babel and
> radio lists in terms of org-elements. Maybe I am insane, as you imply.
I never wrote, implied or even thought you were insane.
> What if I rewrote org-babel-read-list in terms of org-elements? That
> would satisfy me wrt. babel, and wouldn’t necessitate disturbing
> org-list-parse-list, radio lists, or indeed anything outside of babel.
That is even better.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-09-28 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 19:17 [RFC] [PATCH] [babel] read description lists as lists of lists Aaron Ecay
2014-09-20 0:30 ` Charles Berry
2014-09-20 11:52 ` Nicolas Goaziou
2014-09-23 4:02 ` Aaron Ecay
2014-09-24 19:56 ` Nicolas Goaziou
2014-09-24 22:49 ` Aaron Ecay
2014-09-26 9:03 ` Nicolas Goaziou
2014-09-28 5:55 ` Aaron Ecay
2014-09-28 10:49 ` Thorsten Jolitz
2014-09-28 22:09 ` 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=8761g7wg6v.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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 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.