From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Blank page in LaTeX/PDF output
Date: Fri, 28 Feb 2014 13:32:57 -0500 [thread overview]
Message-ID: <5310D659.1060707@pfdstudio.com> (raw)
In-Reply-To: <5310D314.7040709@pfdstudio.com>
On 2/28/14, 1:19 PM, Peter Davis wrote:
>
> On 2/28/14, 12:37 PM, John Hendy wrote:
>> You can also try:
>>
>> #+latex: \scriptsize % or \small, \footnotesize, or \tiny
>>
>> before your table to make it smaller as well if you think that's
>> contributing.
>
> These seem like things to try after the content is completely locked
> down. Any edits after this could conceivably re-introduce the problem,
> requiring further tweaks.
>
I just found that adding or removing "num:nil" from the #+options:
changes whether or not the blank page appears. I would have thought
header numbering only affects horizontal line length (None of the
headers wrap to more than one line), but apparently I'm wrong. Setting
"toc:nil" got rid of the blank page, but removing "num:nil"
re-introduced it.
Weird.
Thanks!
-pd
--
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
next prev parent reply other threads:[~2014-02-28 18:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:59 Blank page in LaTeX/PDF output Peter Davis
2014-02-28 17:03 ` John Hendy
2014-02-28 17:26 ` Peter Davis
2014-02-28 17:36 ` Peter Davis
2014-02-28 17:37 ` John Hendy
2014-02-28 18:19 ` Peter Davis
2014-02-28 18:32 ` Peter Davis [this message]
2014-03-01 0:38 ` Nick Dokos
2014-03-01 1:21 ` Peter Davis
2014-03-01 1:27 ` John Hendy
2014-03-01 13:01 ` Nick Dokos
2014-03-01 1:30 ` Peter Davis
2014-03-01 3:32 ` Nick Dokos
2014-03-01 3:39 ` Peter Davis
2014-03-01 5:27 ` John Hendy
2014-03-01 12:47 ` Nick Dokos
2014-03-01 14:48 ` Peter Davis
2014-03-01 19:19 ` John Hendy
2014-03-04 0:51 ` Peter Davis
2014-03-04 1:08 ` John Hendy
2014-03-04 1:13 ` Peter Davis
2014-03-04 3:46 ` John Hendy
2014-03-04 12:27 ` Peter Davis
2014-03-01 14:42 ` Nick Dokos
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=5310D659.1060707@pfdstudio.com \
--to=pfd@pfdstudio.com \
--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).