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: [babel] Bugs for Emacs Lisp code blocks
Date: Sat, 06 Apr 2013 17:44:03 +0200	[thread overview]
Message-ID: <868v4v1x6k.fsf@somewhere.org> (raw)

Hello,

Here are some tests with the colnames parameter *and* the Emacs Lisp language
for the "echo" code block. They're giving results I don't understand...

Note that functionally the same "echo" code block in other languages (I tested
R and sh) does return the expected results.

* Input table

Consider this input table, with 2 rows, and a header row.

#+name: input
| id   | var1 |
|------+------|
| obs1 | foo  |
| obs2 | bar  |

* Interactive calls

Let's try different calls, changing the =:colnames= parameter.

1. Using =:colnames yes=

   #+name: ELisp-echo-1
   #+begin_src emacs-lisp :var data=input :colnames yes :exports results
   data
   #+end_src

   #+results: ELisp-echo-1
   | id   | var1 |
   |------+------|
   | obs1 | foo  |
   | obs2 | bar  |

   OK; the result is what I expected.

2. Using =:colnames no=

   #+name: ELisp-echo-2
   #+begin_src emacs-lisp :var data=input :colnames no :exports results
   data
   #+end_src

   #+results: ELisp-echo-2
   | id   | var1 |
   |------+------|
   | obs1 | foo  |
   | obs2 | bar  |

   Here, I was expecting:

   | id   | var1 |
   | obs1 | foo  |
   | obs2 | bar  |

3. Using no =:colnames= header argument

   #+name: ELisp-echo-3
   #+begin_src emacs-lisp :var data=input :exports results
   data
   #+end_src

   #+results: ELisp-echo-3
   | id   | var1 |
   |------+------|
   | obs1 | foo  |
   | obs2 | bar  |

   Here, I was expecting:

   | obs1 | foo |
   | obs2 | bar |

* Call at export time

#+call: ELisp-echo-1(data=input)

I get:

| id   | var1 |
| id   | var1 |
| obs1 | foo  |
| obs2 | bar  |

Not at all what I was expecting...

Best regards,
  Seb

-- 
Sebastien Vauban

             reply	other threads:[~2013-04-06 15:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 15:44 Sebastien Vauban [this message]
2013-04-07 13:29 ` [babel] Bugs for Emacs Lisp code blocks 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

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=868v4v1x6k.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).