From: Julius Dittmar <Julius.Muller@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] Export to latex truncates long subsections (WE attached)
Date: Mon, 26 Aug 2019 12:12:41 +0200 [thread overview]
Message-ID: <5e1d7a4b-9026-a389-2bce-fb059f432a94@gmx.net> (raw)
In-Reply-To: <CA+A2iZb+xk=sNh+BKsy-cpTjag1kV2ZM6iTS_xWxrrAOkgMe3A@mail.gmail.com>
Hi Vladimir,
I see two problems in the generated LaTeX-file you'd need to address.
First, LaTeX has problems handling URLs in section (or subsection)
headers. That's one of the reasons LaTeX chokes on the second run of
that file -- it's only partially generated, not completely.
The second is the fact that there's no content in all those subsections.
I guess that's why LaTeX's page break algorithm fails: It does not want
to make a page break immediately after a section heading. Thus there's
no viable place for LaTeX to break that page.
As there's no contents in all those subsections, how about changing it
to a list with checkboxes? Then the problem with the URLs is solved too.
HTH,
Julius
Am 26.08.19 um 05:46 schrieb Vladimir Nikishkin:
> I have a problem in that when I try to export an .org file into
> latex/pdf, long sections are not wrapped to the next page, but are
> truncated instead.
prev parent reply other threads:[~2019-08-26 10:12 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
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 [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=5e1d7a4b-9026-a389-2bce-fb059f432a94@gmx.net \
--to=julius.muller@gmx.net \
--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).