emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] Export to latex truncates long subsections (WE attached)
Date: Thu, 19 Nov 2020 15:58:24 +1100	[thread overview]
Message-ID: <87sg96ymbz.fsf@gmail.com> (raw)
In-Reply-To: <CA+A2iZa_D1NHjti4sZxH3OZugTH4Phmp6vgMeDGeHv08y-EasQ@mail.gmail.com>


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

At the very least, something should probably be put on worg so that
anyone who is running into the page breaking issue can add the snippet
using file header lines.

--
Tim Cross


  reply	other threads:[~2020-11-19  4:59 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
2019-08-27  8:10       ` Tim Cross
2020-11-19  3:41     ` Vladimir Nikishkin
2020-11-19  4:58       ` Tim Cross [this message]
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:
  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=87sg96ymbz.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: [bug] Export to latex truncates long subsections (WE attached)' \
    /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 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).