From: Rainer M Krug <r.m.krug@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: "Wrapping" section into LaTeX statements?
Date: Mon, 14 May 2012 09:33:20 +0200 [thread overview]
Message-ID: <4FB0B540.7030101@gmail.com> (raw)
In-Reply-To: <m162c2u2vh.fsf@tsdye.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/05/12 17:57, Thomas S. Dye wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> Hi
>>
>> I want to wrap a section of a document into LaTeX statements, as I would like to redefine
>> \subsectionbreak so that it does a \pagebreak before - but *only in one section*:
>>
>> * A normal section * Here I want the redefinition #+BEGIN_LaTeX \let\oldsubsection =
>> \subsection \renewcommand{\subsection}[1]{ \pagebreak{} \oldsubsection{#1} } #+END_LaTeX **
>> subsection 1 ** subsection 2 * And here I want to use the old sectionbreak #+BEGIN_LaTeX
>> \renewcommand{\subsection}[1]{ \oldsubsection{#1} } #+END_LaTeX ** subsection 1 ** subsection
>> 2
>>
>> Now I can do this as above, but I don't like it, as the second LaTeX code actually should be
>> at the end of the previous section and if I insert a section, I have to move the LaTeX code.
>>
>> I could put it into the previous section, but then it would be in the subsection 2, and if I
>> add a subsection 3, I would have to move the LaTeX code into this subsection.
>>
>> So nothing is optimal - is there an alternative which makes more sense and is easier to
>> maintain?
>>
>> Thanks,
>>
>> Rainer
> Aloha Rainer,
>
> * section
>
> \pagebreak ** subsection 1 ** subsection 2
>
> Would this work? Note that \pagebreak doesn't have a required argument--the optional argument
> \pagebreak[] lets LaTeX decide whether or not to break the page.
Thank - but I would like to have a pagebreak before *each* subsection in a section. Without doubt,
I could use \pagebreak before each subsection header, but it is easier to redefine \subsection{}
for this section and to set it back to the original afterwards.
Cheers,
Rainer
>
> All the best, Tom
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+wtUAACgkQoYgNqgF2ego7CwCfUQPBlgb1cP7H09zbBq851ic7
uXkAniynkWja3ZpoQN5TPGTNcBPos6pv
=L3vX
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-05-14 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 9:43 "Wrapping" section into LaTeX statements? Rainer M Krug
2012-05-11 15:57 ` Thomas S. Dye
2012-05-14 7:33 ` Rainer M Krug [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=4FB0B540.7030101@gmail.com \
--to=r.m.krug@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
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).