From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [babel] Bugs for Emacs Lisp code blocks Date: Mon, 15 Apr 2013 16:04:52 +0200 Message-ID: <86zjwzevp7.fsf@somewhere.org> References: <868v4v1x6k.fsf@somewhere.org> <871uamo4e9.fsf@gmail.com> <86d2u6z6kg.fsf@somewhere.org> <87d2u65dr1.fsf@gmail.com> <86wqsbcws2.fsf@somewhere.org> <87k3o7e5kq.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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