From: Eric Schulte <schulte.eric@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel: the disappearing hline
Date: Mon, 11 Nov 2013 09:19:51 -0700 [thread overview]
Message-ID: <87y54uhpw8.fsf@gmail.com> (raw)
In-Reply-To: <87wqkfrm3v.fsf@gmail.com> (Thorsten Jolitz's message of "Mon, 11 Nov 2013 16:31:32 +0100")
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Jarmo Hurri <jarmo.hurri@syk.fi> writes:
>
>>>> While taking my first long tour in the land of Babel, I bumped into a
>>>> minor hline issue. Can someone tell me why the hline has disappeared
>>>> from the second table?
>>>
>>> Because you use CALL without arguments and argument :hlines defaults
>>> to 'no'?
>>
>> Ok, but why is there then a hline in the raw output in table-three?
>> Furthermore, setting hlines to yes makes no difference:
>
> * test
> #+NAME: table-one
> #+BEGIN_SRC emacs-lisp
> (list '(a) '(b) 'hline '(c))
> #+END_SRC
>
> #+results: table-one
> | a |
> | b |
> |---|
> | c |
>
>
> #+NAME: table-two
> #+CALL: table-one[:hlines yes]()
> #+results: table-two
> | a |
> | b |
> | c |
>
> but
>
> #+begin_src emacs-lisp :var table=table-one :hlines yes
> table
> #+end_src
>
> #+results:
> | a |
> | b |
> |---|
> | c |
>
> seems to be a problem with #+CALL then ...
The ":hlines yes" header argument must be set on the call line itself.
See (info "(org)Evaluating code blocks").
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: call.org --]
[-- Type: text/x-org, Size: 340 bytes --]
* test
#+NAME: table-one
#+BEGIN_SRC emacs-lisp
(list '(a) '(b) 'hline '(c))
#+END_SRC
#+results: table-one
| a |
| b |
|---|
| c |
#+NAME: table-two-without
#+CALL: table-one()
#+results: table-two-without
| a |
| b |
| c |
#+NAME: table-two-with
#+CALL: table-one() :hlines yes
#+results: table-two-with
| a |
| b |
|---|
| c |
[-- Attachment #3: Type: text/plain, Size: 63 bytes --]
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-11-11 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:35 Babel: the disappearing hline Jarmo Hurri
2013-11-11 14:53 ` Thorsten Jolitz
2013-11-11 15:11 ` Jarmo Hurri
2013-11-11 15:31 ` Thorsten Jolitz
2013-11-11 16:19 ` Eric Schulte [this message]
2013-11-11 17:26 ` Jarmo Hurri
2013-11-11 17:44 ` Eric Schulte
2013-11-12 6:16 ` Jarmo Hurri
2013-11-12 15:45 ` Rick Frankel
2013-11-12 16:09 ` Jarmo Hurri
2013-11-12 19:22 ` Rick Frankel
2013-11-13 6:19 ` Jarmo Hurri
2013-11-13 14:17 ` Eric Schulte
2013-11-13 18:52 ` Rick Frankel
2013-11-13 23:27 ` Eric Schulte
2013-11-15 6:50 ` Jarmo Hurri
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=87y54uhpw8.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.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).