emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: jman <emacs-orgmode@city17.xyz>
To: Christian Moe <mail@christianmoe.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Understanding Publish (ox-publish.el)
Date: Mon, 14 Oct 2024 20:47:00 +0200	[thread overview]
Message-ID: <87ed4ittcr.fsf@city17.xyz> (raw)
In-Reply-To: <877caavgj8.fsf@city17.xyz> (jman's message of "Mon, 14 Oct 2024 17:40:59 +0200")


jman <emacs-orgmode@city17.xyz> writes:

> 2) Compiling this other document will produce strange empty pages. The content of the ordered list
> doesn't fit one page and instead of filling the next page, it will just "overflow" and 
> "disappear":
> https://paste.sr.ht/~jman/35434b0fdf08164abf6c59a413d60ea6a4d0e943

I think the problem is that for the above file is a single ordered list and org-mode (or Latex?) for 
some reason are unable to split it. For an automatic split to happen, the single list must be split.

So another hack is to add random text in between! Example:

#+TITLE: Dokument Titel
#+LATEX_HEADER: \usepackage[paper=a4paper,top=3cm,bottom=3cm]{geometry}
* Title 1
** Subtitle
*** Subsubtitle
* Title 2
** Subtitle
*** Subsubtitle
* Title 3
** Subtitle
*** Subsubtitle
This text here is only to split the ordered list.
* Title 4
** Subtitle
*** Subsubtitle
* Title 5
** Subtitle
*** Subsubtitle
This text here is only to split the ordered list.
(etc.)

Now we have multiple lists and the page split happens according to the top and bottom margins set in 
the header.

I am not sure if there is a better way to work around this.

Best,


  reply	other threads:[~2024-10-14 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 19:25 Understanding Publish (ox-publish.el) jman
2024-10-14  8:37 ` Christian Moe
2024-10-14 15:40   ` jman
2024-10-14 18:47     ` jman [this message]
2024-10-14 21:06       ` Christian Moe
2024-10-15  7:13         ` jman
2024-10-15  8:11           ` Christian Moe
2024-10-15 11:54             ` Rens Oliemans
2024-10-14 10:02 ` Dr. Arne Babenhauserheide

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=87ed4ittcr.fsf@city17.xyz \
    --to=emacs-orgmode@city17.xyz \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    /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).