From: "Sébastien Miquel" <email@example.com> To: Nicolas Goaziou <firstname.lastname@example.org> Cc: emacs-orgmode <email@example.com> Subject: Re: [patch] fix ox-latex async export bug Date: Tue, 30 Nov 2021 11:58:07 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi, Nicolas Goaziou writes: > This is not really the same fix. Indeed, but I tested it and it does work. > You're quoting a lambda, which should > not be required if the problem disappeared. IOW, the true fix probably > belong in the `org-export-async-start' function. What happens is as follows 1. This lambda is passed as the =post-process= variable of =org-export-to-file=. 2. Which converts it to code using =`(funcall ',post-process)= 3. Which =org-export-async-start= writes to a file, to be executed by the external emacs process. I think native compilation compiles the lamdba in =org-latex-export-to-pdf= and that there is no way to get back this original lambda (the code) from within =org-export-to-file= or =org-export-async-start=. Quoting the lambda prevents this compilation. My understanding of elisp and the native compilation business is quite superficial, so this may be wrong. Regards, -- Sébastien Miquel
next prev parent reply other threads:[~2021-11-30 11:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-28 15:59 Rasmus 2021-11-28 19:52 ` Nicolas Goaziou 2021-11-28 22:54 ` Tim Cross 2021-11-29 5:15 ` Timothy 2021-11-30 19:46 ` Rasmus 2021-11-29 9:19 ` Sébastien Miquel 2021-11-29 21:39 ` Nicolas Goaziou 2021-11-30 11:58 ` Sébastien Miquel [this message] 2021-12-10 9:30 ` Nicolas Goaziou 2021-11-30 19:35 ` Rasmus Pank Roulund 2021-12-01 6:40 ` Sébastien Miquel 2021-12-01 8:06 ` Rasmus
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [patch] fix ox-latex async export bug' \ /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
Code repositories for project(s) associated with this 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).