From: Julius Dittmar <Julius.Dittmar@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] Export to latex truncates long subsections (WE attached)
Date: Thu, 19 Nov 2020 10:42:35 +0100 [thread overview]
Message-ID: <9675db8f-2c7d-97e9-805c-c9cfe0c711b3@gmx.de> (raw)
In-Reply-To: <87sg96ymbz.fsf@gmail.com>
Am 19.11.20 um 05:58 schrieb Tim Cross:
>
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
>> So what is the status of this story?
>>
>> I believe that if one exports an org file with sufficiently many empty
>> TODO headings (to me, it seems a perfectly valid use case of org,
>> printing lists of TODOs), they won't fit on a single page, and latex
>> will drop them. Would the latex snippet in this thread be a good
>> candidate for inclusion into org as a canned trick?
>>
>> On Tue, 27 Aug 2019 at 14:57, Vladimir Nikishkin <lockywolf@gmail.com> wrote:
>>>
>>> I have indeed investigated the issue, and this is the link:
>>> https://latex.org/forum/viewtopic.php?f=47&t=32788
>>>
>>> To make the long story short, the folowing trick is needed to allow
>>> page breaks after headings (which is a completely standard case in
>>> -org).
>>>
>>> #+begin_src latex
>>> \usepackage{xpatch}
>>> \makeatletter
>>> % This is not recommended, because it can break several things
>>> \xpatchcmd{\@afterheading}{\@nobreaktrue}{\@nobreakfalse}{%
>>> \typeout{WARNING: \string\@afterheading\space broken}%
>>> }{%
>>> \@latexerr{ERROR: Cannot patch \string\@afterheading}\@ehd%
>>> }
>>> \makeatother
>>> #+end_src
>>>
>>> Shall this trick be considered for inclusion in 'org' officially?
>>> I mean, having lists of empty headings is a perfectly standard use case for org.
>>>
>
> What are the implications of doing this? In particular, the comment
>
>>> % This is not recommended, because it can break several things
>
> Many people have quite complex environments for generating Latex and we
> would need to be certain that adding this package doesn't 'break several
> things'.
For one thing, it allows something (La)TeX tries to circumvent: page
breaks immediately after a section heading. In normal documents, that's
something you want to avoid as much as possible.
Perhaps another approach would be more fitting, but it needs changing
the LaTeX output routine: Have org add something invisible after a
heading in case that heading's body is empty. That makes page breaks
possible (after that invisible something) without changing the behaviour
for non-empty sections.
Just my thoughts,
Julius Dittmar
next prev parent reply other threads:[~2020-11-19 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 3:46 [bug] Export to latex truncates long subsections (WE attached) Vladimir Nikishkin
2019-08-26 9:47 ` Nicolas Goaziou
2019-08-27 6:57 ` Vladimir Nikishkin
2019-08-27 7:42 ` Julius Dittmar
2019-08-27 8:10 ` Tim Cross
2020-11-19 3:41 ` Vladimir Nikishkin
2020-11-19 4:58 ` Tim Cross
2020-11-19 9:42 ` Julius Dittmar [this message]
2020-11-19 10:13 ` Eric S Fraga
2020-11-19 11:28 ` Tim Cross
2020-11-19 12:09 ` Eric S Fraga
2020-11-19 11:09 ` Maxim Nikulin
2019-08-26 10:12 ` Julius Dittmar
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=9675db8f-2c7d-97e9-805c-c9cfe0c711b3@gmx.de \
--to=julius.dittmar@gmx.de \
--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).