From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Kowalczyk Subject: Long clocktable runs off page (PDF export). Page-break and flow to next page? Date: Sat, 09 May 2009 08:50:39 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M2m1C-0002Q1-2w for emacs-orgmode@gnu.org; Sat, 09 May 2009 08:51:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M2m17-0002NR-Fu for emacs-orgmode@gnu.org; Sat, 09 May 2009 08:51:05 -0400 Received: from [199.232.76.173] (port=55908 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M2m17-0002N6-BI for emacs-orgmode@gnu.org; Sat, 09 May 2009 08:51:01 -0400 Received: from main.gmane.org ([80.91.229.2]:44723 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M2m16-0002ia-VI for emacs-orgmode@gnu.org; Sat, 09 May 2009 08:51:01 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M2m12-00033o-A0 for emacs-orgmode@gnu.org; Sat, 09 May 2009 12:50:56 +0000 Received: from 75-94-107-246.roc.clearwire-dns.net ([75.94.107.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 May 2009 12:50:56 +0000 Received: from jtk by 75-94-107-246.roc.clearwire-dns.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 May 2009 12:50:56 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org When my worklog clocktable gets longer than the PDF export page, it simply runs off the bottom of the page. Is there a LaTeX-customization (and/or consider this a feature request) such that the table could page-break and flow to the next page at any row? #+BEGIN: clocktable :maxlevel 2 :scope subtree The worklogs are simple: one L1 heading, and many clocked L2 tasks. There are often several day's gaps between L2 tasks, so I don't use the step and tstart tend clocktable options Thanks, Jeff