From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-babel :colnames yes
Date: Thu, 28 May 2020 09:29:43 -0400 [thread overview]
Message-ID: <87y2pcrxvc.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CAC=rjb56PC+dazpDtV=Je-+POWaZ7z_O3Bbt-yCQpgHsmqCZJg@mail.gmail.com
Would this work for you?
--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC elisp :colnames yes
'((one two) hline (1 3) (1 6))
#+END_SRC
#+RESULTS:
| one | two |
|-----+-----|
| 1 | 3 |
| 1 | 6 |
--8<---------------cut here---------------end--------------->8---
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2020-05-28 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 11:48 org-babel :colnames yes ian martins
2020-05-28 13:29 ` Nick Dokos [this message]
2020-05-28 13:44 ` ian martins
2020-05-29 2:08 ` ian martins
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=87y2pcrxvc.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.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).