From: Tim Cross <firstname.lastname@example.org>
Subject: Re: [BUG] Async pdf export broken with native-comp
Date: Fri, 16 Jul 2021 09:15:05 +1000 [thread overview]
Message-ID: <email@example.com> (raw)
Sébastien Miquel <firstname.lastname@example.org> writes:
> The async pdf export functionality appears to be broken with latest org and a
> recent emacs version compiled with native-comp enabled (I have not tested
> without native-comp).
> To reproduce:
> - use `emacs -q` and an empty init.el file (your init file gets picked up by
> the async emacs instance)
> - (setq org-export-async-debug t)
> - find any org file and hit =C-c C-e C-a C-l C-p= to export as pdf file.
> The async process will exit abnormaly.
> The issue stems from this line in `org-export-to-file`
> : (ignore-errors (funcall ',post-process ,file))
> In `org-latex-export-to-pdf`, this `post-process` is set to
> : (lambda (file) (org-latex-compile file))
> I think native-comp compiles this lambda, which messes things up.
> As a fix, you can quote the lambda in `org-latex-export-to-pdf`
> : '(lambda (file) (org-latex-compile file))
> The same applies to other backends but I don't know if it's the right thing to
I think native comp has a way to go before we begin to worry about how
to address any bugs which it may introduce/discover. While it is good to
have information like this posted to the list for anyone who wants to
experiment with native comp, it would be premature to apply any fixes to
the org code base.
next prev parent reply other threads:[~2021-07-15 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 17:45 [BUG] Async pdf export broken with native-comp Sébastien Miquel
2021-07-15 23:15 ` Tim Cross [this message]
2021-07-15 23:36 ` Mark Barton
2021-07-16 6:05 ` Timothy
2021-07-16 6:31 ` Tim Cross
2021-07-16 9:32 ` Sébastien Miquel
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 \
* 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
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).