From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: [babel] lisp block evaluation vs. call
Date: Thu, 22 Mar 2012 09:26:28 +0100 [thread overview]
Message-ID: <871uolqbwr.fsf@med.uni-goettingen.de> (raw)
Hi all,
Say, I have a lisp function working on (and returning a) table:
#+name: insert_hline
#+header: :var fulltable=testtable :var after_row=1
#+begin_src emacs-lisp
(let ((rrr (cons (quote hline) fulltable))
(bottomrows (nthcdr after_row fulltable))
(toprows (reverse (nthcdr (- (length fulltable) after_row) (reverse fulltable)))))
(setcdr rrr bottomrows)
(setcdr (nthcdr (- after_row 1) fulltable) rrr)
fulltable)
#+end_src
Now, I want to apply it on this testtable:
#+name: testtable
| parameter | value |
| amount | 1 |
| margin | 12 |
When evaluated directly, this works fine and as expected:
#+results: insert_hline
| parameter | value |
|-----------+-------|
| amount | 1 |
| margin | 12 |
But when I call this code block, I miss the header, even though the
manual states
#+begin_quote
For example Emacs Lisp code blocks ignore the :colnames header
argument entirely given the ease with which tables with column names
may be handled directly in Emacs Lisp.
#+end_quote
#+call: insert_hline(fulltable=testtable, after_row=1)
#+results: insert_hline(fulltable=testtable, after_row=1)
| amount | 1 |
| margin | 12 |
If I want to get the header back, I have to explicitly
state ':colnames yes'
#+call: insert_hline(fulltable=testtable,after_row=1) :colnames yes
#+results: insert_hline(fulltable=testtable,after_row=1)
| parameter | value |
|-----------+-------|
| amount | 1 |
| margin | 12 |
I guess, that inconsistency I will have to live with?
Best regards,
Andreas
next reply other threads:[~2012-03-22 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 8:26 Andreas Leha [this message]
2012-03-22 8:54 ` [babel] lisp block evaluation vs. call Andreas Leha
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=871uolqbwr.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).