Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-28 Thread Thorsten Jolitz
Aaron Ecay aarone...@gmail.com writes: Hi Aaron, So the question is, how to provide a consistent language-agnostic view of org structure to other languages. well, that would be the parse-tree normally, its a nested list containing all info about org structure. I tried to make two Lisps

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-28 Thread Nicolas Goaziou
Aaron Ecay aarone...@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

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-27 Thread Aaron Ecay
Hi Nicolas, 2014ko irailak 26an, Nicolas Goaziou-ek idatzi zuen: Why? Babel’s representation is for babel. Which I strongly frown upon. 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

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-26 Thread Nicolas Goaziou
Hello, Aaron Ecay aarone...@gmail.com writes: Isn’t the org-element format also easy to work on? It requires a bit more than just car and cdr, but it’s well documented and used in many places across the code base (= cognitive burden to use is lower). It’s also easy to produce in the sense

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-24 Thread Nicolas Goaziou
Hello, Aaron Ecay aarone...@gmail.com writes: I think I can remove these three functions (-parse-list, -to-subtree, and -to-generic), and rewrite their callers to use org-element. Thus, the org-list-parse-list format would be eradicated from the code base incl. contrib (AFAICT). Can I do

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-24 Thread Aaron Ecay
Hi Nicolas, Thanks for the discussion. 2014ko irailak 24an, Nicolas Goaziou-ek idatzi zuen: You cannot do that. This is not about backwards compatibility. `org-list-parse-list' generates an easy to produce and work on internal representation for lists (similar to what `org-table-to-lisp'

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-22 Thread Aaron Ecay
Hi Nicolas, Thanks for your feedback. 2014ko irailak 20an, Nicolas Goaziou-ek idatzi zuen: The problem I see here is that you're introducing yet another internal representation for lists (along with element's and org-list-parse-list's). Worse, it can only be discovered when reading the

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-20 Thread Nicolas Goaziou
Hello, Aaron Ecay aarone...@gmail.com writes: The attached patch makes babel read description lists as lists of the following format: ((term description) ...). The present default is to simply read in the text of each list item, yielding: (term :: description ...). Thank you. Of course,

[O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-19 Thread Aaron Ecay
Hello all, The attached patch makes babel read description lists as lists of the following format: ((term description) ...). The present default is to simply read in the text of each list item, yielding: (term :: description ...). Of course, it’s possible to interconvert between the two

Re: [O] [RFC] [PATCH] [babel] read description lists as lists of lists

2014-09-19 Thread Charles Berry
Aaron Ecay aaronecay at gmail.com writes: Hello all, The attached patch makes babel read description lists as lists of the following format: ((term description) ...). The present default is to simply read in the text of each list item, yielding: (term :: description ...). Of