From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: "M. Pger" <mpger@protonmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: asynchronous export (org-mode 9.4.4, emacs 27.2)
Date: Tue, 8 Mar 2022 14:51:30 +0000 [thread overview]
Message-ID: <502bb7ca-d8b5-8841-8817-62268b26a1f4@posteo.eu> (raw)
In-Reply-To: <3aI_0RWdtYHToaSoFmqmpyAUSR2KZku0axL8-LJUUMFhX4_R07b4wTxBx9zJZuEOwHnYrtM5vUDtBtpTz3BgfAFkQC84O1r3uvdeC0cNNIc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
M. Pger writes:
> Thx for your answer. I've just upgraded org-mode (elpa way) and I am
> now using version 9.5.2.
Version 9.5.2 should indeed contain the fix I had in mind :
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c91271297dbbfc831874d7880343603881bdac9c
> Unfortunately this does not work, I still end up with:
>
> Invalid read syntax: "#"
Can you check that the right version of org-mode is picked-up, with
`describe-function` `org-latex-export-to-pdf`, find the function
definition by following the `ox-latex.el` link, and check that the
source contains the linked patch ?
> I would like to try the alternative, i.e. disabling native-comp (for
> the export function I guess). Would you mind telling me how to do that?
`describe-function` should also tell you whether the function is
native compiled. If it is, you can temporarily 'uncompile' by
evaluating its source code. By disabling native compilation I meant as
a compile flag, if you've built emacs from source. I cannot find an
easy way to prevent native compilation of a single package/function.
--
Sébastien Miquel
[-- Attachment #2: Type: text/html, Size: 2968 bytes --]
next prev parent reply other threads:[~2022-03-08 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 12:07 Bug: asynchronous export (org-mode 9.4.4, emacs 27.2) M. Pger
2022-03-08 13:30 ` Sébastien Miquel
2022-03-08 14:12 ` M. Pger
2022-03-08 14:51 ` Sébastien Miquel [this message]
2022-03-08 22:39 ` M. Pger
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=502bb7ca-d8b5-8841-8817-62268b26a1f4@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--cc=emacs-orgmode@gnu.org \
--cc=mpger@protonmail.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).