emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julius Dittmar <Julius.Dittmar@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] Export to latex truncates long subsections (WE attached)
Date: Tue, 27 Aug 2019 09:42:25 +0200	[thread overview]
Message-ID: <17ebee89-8f57-0a92-b708-532340aa0903@gmx.de> (raw)
In-Reply-To: <CA+A2iZZc0HPywzrF9NWho0WJ757RGBGXgT9_m_pH9=b8R_y1+A@mail.gmail.com>

Hi folks,

Am 27.08.19 um 08:57 schrieb Vladimir Nikishkin:
> 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.

I would not want that as the default. Yes, it is one standard use case.
It would break other standard use cases, like creating ordinary
documents, though.

Perhaps variant adding such a patch could be added to org-latex-classes,
or at least mentioned in the docs to org-latex-classes? That way you can
use this "class" version for such cases without adding unnecessary
uglyness to other org-created documents.

Another possible approach would be a change in the export functions.
What really is needed here, from my point of view, is that the export
adds a superficial paragraph to a heading in the case that there's no
content at all. Nothing should be added if the heading has sub-headings,
I count that as content. In case there is no content at all, then some
form of breakable vertical space should be added. I don't know enough
LaTeX to find the least intrusive way, though I'd try \vspace{0pt}.

I did never dig into the export functions, so I don't know how difficult
that would be.

Just my thoughts,
Julius Dittmar

  reply	other threads:[~2019-08-27  7:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  3:46 Vladimir Nikishkin
2019-08-26  9:47 ` Nicolas Goaziou
2019-08-27  6:57   ` Vladimir Nikishkin
2019-08-27  7:42     ` Julius Dittmar [this message]
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

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:

  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=17ebee89-8f57-0a92-b708-532340aa0903@gmx.de \
    --to=julius.dittmar@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: [bug] Export to latex truncates long subsections (WE attached)' \


* 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 inbox:


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