From: "M. Pger" <mpger@protonmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>, sebastien.miquel@posteo.eu
Subject: Re: Bug: asynchronous export (org-mode 9.4.4, emacs 27.2)
Date: Tue, 08 Mar 2022 22:39:13 +0000 [thread overview]
Message-ID: <aw_wwlJcCuUcOWTA5vHxOQaat4W5s33Auov2jBSfrpkgCoM2JuGIUN6WNDQMfBYQL2NQog7cewykBnCPQa2ZuRr0Nc0mwyf4A_yEyYvxxZM=@protonmail.com> (raw)
In-Reply-To: <502bb7ca-d8b5-8841-8817-62268b26a1f4@posteo.eu>
[-- Attachment #1: Type: text/plain, Size: 3377 bytes --]
Ok, thanks a lot for your suggestions. It seems that the problem comes from
poly-org mode. I've followed the following steps (copy-paste from my notes,
sorry for the wording):
+ I double-check the version of org (9.5.2, ok) and I check the function
=org-latex-export-to-pdf=. This is ok since the fix is there:
#+begin_example
(let ((outfile (org-export-output-file-name ".tex" subtreep)))
(org-export-to-file 'latex outfile
async subtreep visible-only body-only ext-plist
#'org-latex-compile)))
#+end_example
+ Same error as before when trying to asynchronously export: the =*Org Export
Process*= buffer still gives ~Invalid read syntax: "#"~
+ However, I do these double-checks with my init file loaded. Contrary to ~emacs
-Q~, when I use ~M-x toggle-debug-on-error~ no =*Backtrace*= buffer opens. I
conclude that maybe something linked to my init file is interfering with the
process, preventing the debugger to correctly capture the error.
+ I thus decide to remove everything from my init file (except ~(use-package
org)~) and to try again. However, the issue is still there and the debugger
does not detect it. I note that =poly-org= mode is still (automatically)
loaded at startup, and I decide to use my other computer and to start with a
brand new installation of emacs.
+ On this new emacs version, the only package I install is =org=, in order to
get version 9.5.2. This time, it works: I am able to asynchronously export.
+ I have the impression that having =poly-org= mode installed could play a role
in my problem. I thus decide to get the init file from my other computer and
load it on my new installation of emacs, *except the =polymode= part*. And it
actually works: I am able to asynchronously export.
+ As a final test, I include the =polymode= part of my init file, and restart
Emacs. This time the asynchronous export process fails.
What I conclude from that (correct me if I am wrong): the issue should come from
=polymode= which, once installed, somehow modifies the standard org-export
function/process. I am going to report this issue on the polymode github.
Best,
MP
------- Original Message -------
On Tuesday, March 8th, 2022 at 3:51 PM, Sébastien Miquel <sebastien.miquel@posteo.eu> wrote:
> 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: 6130 bytes --]
prev parent reply other threads:[~2022-03-08 22:40 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
2022-03-08 22:39 ` M. Pger [this message]
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='aw_wwlJcCuUcOWTA5vHxOQaat4W5s33Auov2jBSfrpkgCoM2JuGIUN6WNDQMfBYQL2NQog7cewykBnCPQa2ZuRr0Nc0mwyf4A_yEyYvxxZM=@protonmail.com' \
--to=mpger@protonmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.miquel@posteo.eu \
/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).