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 22:28:23 +1100 [thread overview]
Message-ID: <87ft55ziug.fsf@gmail.com> (raw)
In-Reply-To: <87v9e17ixz.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Thursday, 19 Nov 2020 at 11:41, Vladimir Nikishkin wrote:
>> Would the latex snippet in this thread be a good candidate for
>> inclusion into org as a canned trick?
>
> No, please do not have this as default behaviour. It would break normal
> documents. In the most innocuous case, it would allow documents to have
> headings as the last part of a page with the text on the next page, a
> typesetting faux pas (looking rather ugly). LaTeX documents look
> inherently nicer than the typical word processed document because LaTeX
> actually adjusts spacing of not only within lines but also between lines
> and paragraphs to have the page look good.
>
> As Tim has suggested, adding this snippet to Worg would be useful and
> maybe an item in the FAQ. As well, it might be useful to suggest
> checkbox lists for people that want to export a long TODO list (which
> might not be appropriate for all, of course).
>
I realised after posting that when this first came up some time back,
the other suggestion I made, which might still be valid, would be to add
another document 'class' to org-latex-classes which includes the snippet
by default. Then those who want or need this change could just add a
#+LATEX_CLASS line to their org file.
Tim
--
Tim Cross
next prev parent reply other threads:[~2020-11-19 11:29 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 [this message]
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=87ft55ziug.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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).