emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Bugs for Emacs Lisp code blocks
Date: Mon, 15 Apr 2013 16:04:52 +0200	[thread overview]
Message-ID: <86zjwzevp7.fsf@somewhere.org> (raw)
In-Reply-To: 87k3o7e5kq.fsf@gmail.com

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	other threads:[~2013-04-15 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 15:44 [babel] Bugs for Emacs Lisp code blocks Sebastien Vauban
2013-04-07 13:29 ` Eric Schulte
2013-04-07 15:47   ` Sebastien Vauban
2013-04-07 19:42     ` Eric Schulte
2013-04-08 20:14       ` Sebastien Vauban
2013-04-08 21:07         ` Eric Schulte
2013-04-09  8:13           ` Sebastien Vauban
2013-04-12 22:03             ` Eric Schulte
2013-04-15 13:46               ` Sebastien Vauban
2013-04-09 19:46       ` Sebastien Vauban
2013-04-10  7:54         ` Sebastien Vauban
2013-04-12 22:10           ` Eric Schulte
2013-04-15 14:09             ` Sebastien Vauban
2013-04-15 15:26               ` Eric Schulte
2013-04-12 22:09         ` Eric Schulte
2013-04-15 14:04           ` Sebastien Vauban [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86zjwzevp7.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).