emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [babel] Bugs for Emacs Lisp code blocks


From: Sebastien Vauban
Subject: Re: [O] [babel] Bugs for Emacs Lisp code blocks
Date: Mon, 15 Apr 2013 15:46:33 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (windows-nt)

Eric,

Eric Schulte wrote:
>>>> Let me explain. AFAICT, there were 5 possibles values of the ":colnames"
>>>> header argument:
>>>>
>>>> - no header argument :: (default for all languages but Emacs Lisp)
>>>> - ":colnames no" :: (default for Emacs Lisp code blocks)
>>>> - ":colnames yes" :: Tells Org Babel that your first row contains column
>>>>   names.
>>>> - ":colnames <LIST>" :: Specifies to use <LIST> as column names.
>>>> - ":colnames nil" :: Same as ":colnames yes".
>>>>
>>>> Right?
>>>
>>> Almost, values 1 (none) and 5 (nil) are the same.
>>
>> I don't share your view about this last statement.
>
> As I believe I mentioned "nil" on a header argument is not interpreted
> as the lisp literal `nil'.  To pass an empty argument to a code block
> you should do ":colnames '()", an obscure syntax for an obscure thing.

I do now share your view with your precision on using

- :colnames '() or
- :colnames ()

to pass an empty argument.

Are both version above really equivalent (they _do_ behave the same in my tests,
but I'm wondering for the future)?

Best regards,
  Seb

-- 
Sebastien Vauban




reply via email to

[Prev in Thread] Current Thread [Next in Thread]