From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Bugs for Emacs Lisp code blocks
Date: Fri, 12 Apr 2013 16:03:08 -0600 [thread overview]
Message-ID: <87ppxze5ku.fsf@gmail.com> (raw)
In-Reply-To: 86wqsc6rzs.fsf@somewhere.org
>>>
>>> Much clearer, but not yet crystal-clear for me...
>>>
>>> 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.
>
> ** Input table
>
> #+name: unset-colnames-example-input
> | a | b |
> |---+---|
> | 1 | 2 |
> | 3 | 4 |
>
> ** Having no =:colnames= header argument (case 1)
>
> Same results for R and sh code blocks (first good news ;-)) -- I'm avoiding,
> on purpose, testing with Emacs Lisp...
>
> #+begin_src R :var data=unset-colnames-example-input
> data
> #+end_src
>
> #+results:
> | 1 | 2 |
> | 3 | 4 |
>
> #+begin_src sh :var data=unset-colnames-example-input
> echo "$data"
> #+end_src
>
> #+results:
> | 1 | 2 |
> | 3 | 4 |
>
Looks good.
>
> ** Using =:colnames nil= header argument (case 5)
>
> Once again, R and sh blocks do produce the same results...
>
> #+begin_src R :var data=unset-colnames-example-input :colnames nil
> data
> #+end_src
>
> #+results:
> | a | b |
> |---+---|
> | 1 | 2 |
> | 3 | 4 |
>
> #+begin_src sh :var data=unset-colnames-example-input :colnames nil
> echo "$data"
> #+end_src
>
> #+results:
> | a | b |
> |---+---|
> | 1 | 2 |
> | 3 | 4 |
>
> ... but they are _not_ equivalent to the "no header argument" (case 1).
>
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.
>
> ** Using =:colnames yes= header argument (case 3)
>
> On the contrary, case 5 is equivalent to the case 3: same results as
> ":colnames yes".
>
> #+begin_src R :var data=unset-colnames-example-input :colnames yes
> data
> #+end_src
>
> #+results:
> | a | b |
> |---+---|
> | 1 | 2 |
> | 3 | 4 |
>
> #+begin_src sh :var data=unset-colnames-example-input :colnames yes
> echo "$data"
> #+end_src
>
> #+results:
> | a | b |
> |---+---|
> | 1 | 2 |
> | 3 | 4 |
>
Because the "nil" you specified above is just treated as a string. You
get the same thing with.
#+begin_src sh :var data=unset-colnames-example-input :colnames sure
echo "$data"
#+end_src
#+RESULTS:
| a | b |
|---+---|
| 1 | 2 |
| 3 | 4 |
Cheers,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-04-12 22:40 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 [this message]
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
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=87ppxze5ku.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).