From: Tim Cross <email@example.com>
Subject: Re: [BUG] Async pdf export broken with native-comp
Date: Fri, 16 Jul 2021 16:31:53 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Timothy <email@example.com> writes:
> Mark Barton <firstname.lastname@example.org> writes:
>> I use native-comp, but have not tried the async export yet.
> FWIW I use native-comp (with Doom + my config) and async PDF export
It might be useful for the OP if you could post what commit of Emacs 28
you are running. Native compilation is a moving feast and it could be
either the OP is running an older version (and issue has been fixed) or
a later version (and issue has been recently introduced). Knowing which
commit you are building from might help him identify whether an update
might fix the issue.
One thing I did notice when I was running native-comp was that the
caching strategy was a little hit and miss - it could also be that your
version is not running native compiled org.
When I was trying native compilation, I found that
- native compilation was a bit restrictive - it didn't compile things
correctly in some situations because it didn't load some dependencies
(i.e. you got errors and warning you don't see with normal *.elc
- The caching was a bit hit and miss
- There was no noticeable performance improvement.
I think all of these issues will eventually be addressed as things
mature. However, for now, I don't see any real benefit in enabling
native compilation other than on an academic level.
next prev parent reply other threads:[~2021-07-16 6:44 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
2021-07-15 23:36 ` Mark Barton
2021-07-16 6:05 ` Timothy
2021-07-16 6:31 ` Tim Cross [this message]
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).