emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: Org list <emacs-orgmode@gnu.org>, Jean Louis <bugs@gnu.support>
Subject: Re: How to paginate Babel Lisp output?
Date: Sun, 9 Jul 2017 21:13:08 +0300	[thread overview]
Message-ID: <20170709181308.GB30655@protected.rcdrun.com> (raw)
In-Reply-To: <87mv8d1sus.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me>

On Sun, Jul 09, 2017 at 09:24:11AM -0700, Richard Lawrence wrote:
> Hi Jean,
> 
> Jean Louis <bugs@gnu.support> writes:
> 
> > I have a very simple lisp output within Org Mode file, and it delivers
> > list of lists with 4-5 elements, and it displays nicely as a text.
> 
> (Do you mean: as a table?)
> 
> > #+BEGIN_SRC lisp :exports results  (load
> > #P"/home/data1/protected//lisp/load-some-files.lisp" :verbose nil :print
> > nil) (sku-list-values-by-location :location 1369) #+END_SRC
> > 
> > But when exporting LaTeX I get the result that the table is basically
> > too long, even being printed over the page number and below, and does
> > not even continue on the next page.
> > 
> > Is there a way or customization to make it break pages automatically
> > when there is long output from source blocks?
> 
> If you are already getting your results as an Org table, try adding
> 
> #+ATTR_LATEX: :environment longtable
> 
> to that table.  This will use the LaTeX longtable package and
> environment to format the table, which should take care of breaking it
> across pages.
> 
> Best,
> Richard

That worked well, thank you!

      reply	other threads:[~2017-07-09 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 14:57 How to paginate Babel Lisp output? Jean Louis
2017-07-09 16:24 ` Richard Lawrence
2017-07-09 18:13   ` Jean Louis [this message]

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=20170709181308.GB30655@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=richard.lawrence@berkeley.edu \
    /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).