emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <iemacs@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: #+CALL get the first row of output table lost when using latex export
Date: Mon, 17 Nov 2014 09:43:28 -0500	[thread overview]
Message-ID: <CALeUZPeh+5D3_XpMocoijyA-u0KQ=eE4TNNCJn7jmdL8wmAYwQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20141116T192529-909@post.gmane.org>

Thank you, Charles.  And =:colnames yes= does work here.  But the
results are the same when I evaluate t1 and t2 with
`org-babel-execute-maybe'.

When I take another try, new problem seems to occur.

The test file is:
#+BEGIN_EXAMPLE
#+NAME: t1
#+BEGIN_SRC python :exports results
  return [['A'],None,[2],None,[3]]
#+END_SRC

#+CAPTION: T1
#+RESULTS: t1

#+NAME: t2
#+CALL: t1() :exports results

#+CAPTION: T2
#+RESULTS: t2
#+END_EXAMPLE

The results of `org-babel-execute-maybe' on t1 and t2 are identical:
#+BEGIN_SRC org
  | A |
  |---|
  | 2 |
  |---|
  | 3 |
#+END_SRC

The relevant part of the latex output is:
#+BEGIN_SRC latex
  \begin{table}[htb]
  \caption{T1}
  \centering
  \begin{tabular}{r}
  A\\
  \hline
  2\\
  \hline
  3\\
  \end{tabular}
  \end{table}

  \begin{table}[htb]
  \caption{T2}
  \centering
  \begin{tabular}{r}
  A\\
  2\\
  3\\
  \end{tabular}
  \end{table}
#+END_SRC

Both \hlines in Table T2 are missing.



Kind regards,

Tian Qiu


On Sun, Nov 16, 2014 at 1:37 PM, Charles Berry <ccberry@ucsd.edu> wrote:
>  <iemacs <at> gmail.com> writes:
>
>>
>> Hi,
>>
>> I encounter a problem when I use #+CALL to create a table with latex
>> export.  The problem is that the first row of the table is missing, if
>> the table is created with #+CALL.
>>
> [deleted - setup info]
>
>> The minimal table example is
>>
>> #+BEGIN_EXAMPLE
>> #+NAME: t1
>> #+BEGIN_SRC python :exports results
>>   return [['A'],None,[2]]
>> #+END_SRC
>>
>> #+CAPTION: T1
>> #+RESULTS: t1
>>
>> #+NAME: t2
>> #+CALL: t1() :exports results
>>
>> #+CAPTION: T2
>> #+RESULTS: t2
>> #+END_EXAMPLE
>>
>
> This is not a latex issue per se. If you evaluate t2 with
>
>   `org-babel-execute-maybe'
>
> the same thing will happen.
>
> org-babel-execute:python does its own formatting. #+CALL: OTOH passes
> the results to babel.
>
> The workaround is to use
>
>   #+CALL: t1() :colnames yes
>
> HTH,
>
> Chuck
>
>
>

  reply	other threads:[~2014-11-17 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 15:34 #+CALL get the first row of output table lost when using latex export iemacs
2014-11-16 18:37 ` Charles Berry
2014-11-17 14:43   ` iemacs [this message]
2014-11-17 16:08     ` Charles C. Berry
2014-11-19 14:48       ` iemacs

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='CALeUZPeh+5D3_XpMocoijyA-u0KQ=eE4TNNCJn7jmdL8wmAYwQ@mail.gmail.com' \
    --to=iemacs@gmail.com \
    --cc=ccberry@ucsd.edu \
    --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).