From: tsd@tsdye.com (Thomas S. Dye)
To: John Hendy <jw.hendy@gmail.com>
Cc: York Zhao <gtdplatform@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Force new page on exporting
Date: Tue, 01 Jul 2014 06:31:02 -1000 [thread overview]
Message-ID: <m2zjgtnird.fsf@tsdye.com> (raw)
In-Reply-To: <CA+M2ft9Xs4gr9g_3digNtu2Ni9Y10h32wLcEahMr8eBMDq-KKg@mail.gmail.com> (John Hendy's message of "Tue, 1 Jul 2014 10:06:04 -0500")
Aloha John,
John Hendy <jw.hendy@gmail.com> writes:
> On Mon, Jun 30, 2014 at 11:00 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>> Aloha York,
>>
>> York Zhao <gtdplatform@gmail.com> writes:
>>
>>> Thanks Thomas. This works but is not an ideal approach because in a complex file
>>> it may not be so easy to find out the location to insert the "\newpage"
>>> instruction. Plus, each time when inserting new exported tree between
>>> "Headline1" and "Headline2" you would have to remember to move the "\newpage" to
>>> the end of the new tree.
>>
>>
>> Agreed. Something like this is more visible.
>>
>> * Latex New Page :ignoreheading:
>> #+latex: \newpage
>>
>
> Clever! I was trying to think of a way to do it within headline 3, but
> get it to break before the actual section heading... this much better.
> One question, say the following occurs:
>
> * Heading 1 :export: ...
> * Heading 2
> * Latex New Page :ignoreheading:export:
> #+latex: \newpage
>
> * Heading 3 :export: ...
>
> Say that with \maketitle and possible TOC, Heading 1 ends exactly on
> the last line of page 1. Won't the \newpage command create a full
> blank page on page 2, with Heading 3 starting on page 3?
>
> Rare situation, but just thought I'd inquire about the possibility.
I don't think this is a problem. The LaTeX \newpage command requires
some content on the page before it will work. If it is the first thing
on the page, then no new page is created.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
prev parent reply other threads:[~2014-07-01 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 23:37 Force new page on exporting York Zhao
2014-07-01 0:49 ` Thomas S. Dye
2014-07-01 2:13 ` York Zhao
2014-07-01 4:00 ` Thomas S. Dye
2014-07-01 14:45 ` York Zhao
2014-07-01 15:30 ` Nick Dokos
2014-07-01 15:52 ` York Zhao
2014-07-01 16:21 ` Nick Dokos
2014-07-01 16:59 ` York Zhao
2014-07-01 18:22 ` York Zhao
2014-07-03 16:55 ` York Zhao
2014-07-01 16:12 ` Thomas S. Dye
2014-07-01 15:06 ` John Hendy
2014-07-01 16:31 ` Thomas S. Dye [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=m2zjgtnird.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=gtdplatform@gmail.com \
--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).