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 17:40:59 +0200 [thread overview]
Message-ID: <877caavgj8.fsf@city17.xyz> (raw)
In-Reply-To: <87jzeb9ixl.fsf@christianmoe.com> (Christian Moe's message of "Mon, 14 Oct 2024 10:37:59 +0200")
Christian Moe <mail@christianmoe.com> writes:
> 1. First issue:
>
> Not quite sure what you mean by saying that it "does not handle content
> exceeding the page length". If the problem is with placing images,
> tables etc., latex does its best, and manually adding \clearpage or
> \newpage as needed tends to be the way it's done.
Hey thanks for the tips!
To be clearer about what I mean I'll provide two sample documents. I hope they're good to reproduce
the issue.
1) Compiling with ox-publish the following document produces the expected result. Text is
automatically distributed on subsequent pages
https://paste.sr.ht/~jman/06239fa6624a1af23edfbb5154f5d9dcfdf8427a
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
These samples are compiled with:
$ emacs --batch <file>.org --load ol-pdf.el --funcall org-publish-current-file
`ol-pdf.el` is nothing special, I think:
(require 'ol)
(require 'ox-publish)
(setq org-publish-project-alist
'(("org-to-pdf"
:base-directory "~/src"
:base-extension "org"
:publishing-directory "~/pdf"
:publishing-function org-latex-publish-to-pdf
:recursive t
:with-toc nil
:with-date nil
:with-author nil
)))
Additional info:
- I am using Emacs 29.4 (Org mode 9.6.15)
- I compile these file using the Debian/testing texlive-latex-* (2024.20240829-2) packages
(pdfTeX-1.40.26)
- I also tried compiling the PDF using `latexmk` (4.85) but the end result doesn't change
> 2. Second issue: Getting rid of link borders.
[...]
Thanks! Your suggestions gave me a few ideas to explore and this is now understood.
Best,
next prev parent reply other threads:[~2024-10-14 15:42 UTC|newest]
Thread overview: 12+ 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 [this message]
2024-10-14 18:47 ` jman
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-20 13:04 ` Ihor Radchenko
2024-10-21 7:07 ` Christian Moe
2024-10-26 17:38 ` Ihor Radchenko
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=877caavgj8.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).