emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Blank page in LaTeX/PDF output
Date: Mon, 03 Mar 2014 19:51:08 -0500	[thread overview]
Message-ID: <1393894268.17809.90193409.374029FD@webmail.messagingengine.com> (raw)
In-Reply-To: <CA+M2ft9c72G1-OAKkUau88hPkdu+Wvq2ukWDu1WF+RG9k5TSeQ@mail.gmail.com>


On Sat, Mar 1, 2014, at 02:19 PM, John Hendy wrote:
> I can confirm Peter's results, ...

Thanks, John.

> 
> I searched things like "latex page break 'section*' vs section" with
> no obvious lead on why the two section styles would be different.
> Regarding a bug report, if that's what this is, I just googled "latex
> bugs" and got this page as the first hit:
> - http://latex-project.org/bugs.html
> 


Unfortunately, that site says they can't accept bugs that use any third
party packages, and the org-exported LaTeX file starts:

\documentclass[article,letterpaper,times,12pt,listings-bw,microtype]{scrartcl}
                   \usepackage{microtype}
                    \usepackage{mathpazo}
                   \usepackage[scale=.9]{tgheros}
                   \usepackage{tgcursor}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{amssymb}
\usepackage{hyperref}


Thanks!
-pd


-- 
  Peter Davis
  www.techcurmudgeon.com
  www.timebums.com

  reply	other threads:[~2014-03-04  0:51 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
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 [this message]
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=1393894268.17809.90193409.374029FD@webmail.messagingengine.com \
    --to=pfd@pfdstudio.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@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).