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 16:04:52 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (windows-nt)

Eric,

Eric Schulte wrote:
>> ** Using =:colnames no= header argument (case 2)
>>
>> #+begin_src emacs-lisp :var data=unset-colnames-example-input :colnames no
>>   data
>> #+end_src
>>
>> #+results:
>> | a | b |
>> |---+---|
>> | 1 | 2 |
>> | 3 | 4 |
>>
>> Here, I still don't understand why I do see the table header line: I did
>> change the default =:colnames yes= specification to =:colnames no= on the 
>> code
>> block. I did override the default value. Why is the =no= argument not
>> respected?
>
> Because 'hlines is set to yes by default in
> `org-babel-default-header-args:emacs-lisp'.

I missed the cumulative effect of hlines on the behavior of colnames.
Yes, setting hlines to no does solve the problem for Emacs Lisp code blocks.

Thanks a lot.

Best regards,
  Seb

-- 
Sebastien Vauban




reply via email to

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