[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [Babel] :colnames "no" no longer default for Emacs Lisp [Was] Li
From: |
Eric Schulte |
Subject: |
Re: [O] [Babel] :colnames "no" no longer default for Emacs Lisp [Was] Lisp error: (wrong-type-argument listp hline) |
Date: |
Wed, 02 Oct 2013 07:13:10 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
address@hidden (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.
(add-to-list 'org-babel-default-header-args:emacs-lisp
'(:colnames . "no"))
(add-to-list 'org-babel-default-header-args:emacs-lisp
'(:hlines . "yes"))
You could also change the default emacs lisp header arguments for
certain files with property lines.
Best,
> 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
> anything. Instead of the column names from the original tables, which
> I used to get, I now get names like "t1c2".
>
> All the best,
> Tom
>
> Eric Schulte <address@hidden> writes:
>
>>>
>>> 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 confusion than it
>> is worth. I've reverted this default for elisp, hopefully it doesn't
>> break too many peoples existing Org-mode files.
>>
>> Best,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D