Re: [O] [Babel] :colnames no no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)

2013-10-02 Thread Eric Schulte
t...@tsdye.com (Thomas S. Dye) writes: Hi Eric, I think this breaks Marc-Oliver Ihm's lob-table-operations.org. I use these a lot with #+call: lines. Any tips on how to get the old behavior back? You could add the following to your configuration which would replace the previous default.

Re: [O] [Babel] :colnames no no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)

2013-10-01 Thread Thomas S. Dye
Hi Eric, I think this breaks Marc-Oliver Ihm's lob-table-operations.org. I use these a lot with #+call: lines. Any tips on how to get the old behavior back? I tried :colnames no with one of Marc-Oliver's code blocks, (and kept :colnames yes with my #+call: line) but this didn't seem to change

Re: [O] [Babel] :colnames no no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)

2013-09-30 Thread Sebastien Vauban
Hi Eric, Eric Schulte wrote: I always wondered why emacs-lisp is the _only_ language with :colnames no as its default. Is there a reason therefore? If no really good reason, could we suppress that? This seemed to make sense early on because Emacs Lisp could easily process hlines itself, but

Re: [O] [Babel] :colnames no no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline)

2013-09-28 Thread Eric Schulte
I always wondered why emacs-lisp is the _only_ language with :colnames no as its default. Is there a reason therefore? If no really good reason, could we suppress that? This seemed to make sense early on because Emacs Lisp could easily process hlines itself, but at this point it adds more