emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: York Zhao <gtdplatform@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Force new page on exporting
Date: Mon, 30 Jun 2014 22:13:28 -0400	[thread overview]
Message-ID: <CAD3zm23odBFG0OR8pXpADAqzo5bUCOa4-E5r5s_b00yGOTU7pQ@mail.gmail.com> (raw)
In-Reply-To: <m2tx713nu8.fsf@tsdye.com>

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.

On Mon, Jun 30, 2014 at 8:49 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha York,
>
> York Zhao <gtdplatform@gmail.com> writes:
>
>> I'm selectively exporting some subtree of an org-mode buffer, like this:
>>
>> * Headline1                                                          :export:
>
> #+latex: \newpage
>
>> * Headline2
>> * Headline3                                                          :export:
>>
>> Question is: how do I force Headline3 to be on a new page while exporting to
>> LaTeX?
>
> hth,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com

next prev parent reply	other threads:[~2014-07-01  2:13 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 [this message]
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

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=CAD3zm23odBFG0OR8pXpADAqzo5bUCOa4-E5r5s_b00yGOTU7pQ@mail.gmail.com \
    --to=gtdplatform@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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

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).