From: Max Nikulin <[email protected]>
To: [email protected]
Subject: Re: [BUG] false positive error from org-compile-command [9.7.25 (N/A @ /gnu/store/pya76mlyr24zgwyb6fwv13ab2j04g31h-emacs-org-9.7.25/share/emacs/site-lisp/org-9.7.25/)]
Date: Tue, 12 Aug 2025 21:26:17 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/08/2025 18:04, Christian Moe wrote:
> Ihor Radchenko writes:
>>
>> org-compile-file demanded the compilation target to be newer than .tex
>> source, which is apparently too strong requirement.
>>
>> Fixed, on main.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=499bd92e2
>
> Looks like the new requirement too is too strong. Any latex error during
> the process now causes export to apparently fail with the message:
>
> File "testfile.pdf" wasn't produced
>
> This happens even if the error is non-critical and a PDF /is/ in fact
> produced. So the error message can be misleading.
I agree. May it help if either modification time change *or* zero
command exit code is considered as (at least partial) success?
I admit, I faced the issue in quite specific environment. I do not use
LaTeX extensively, so minimal texlive is enough. Sometimes I am
experimenting with Org LaTeX-related features. To prevent errors, I have
empty files like ulem.sty, amsmath.sty, etc. Since the fix the following
warning became a fatal error
l.10 \usepackage
{amsmath}
The option `normalem' was not declared in package `ulem', perhaps you
misspelled its name. Try typing <return> to proceed.
> On the one hand, this has the merit of alerting me to long-standing,
> non-critical flaws in my setup and documents.
From my point of view, warnings should be warnings: neither hidden nor
fatal.
next prev parent reply other threads:[~2025-08-12 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 11:19 [BUG] false positive error from org-compile-command [9.7.25 (N/A @ /gnu/store/pya76mlyr24zgwyb6fwv13ab2j04g31h-emacs-org-9.7.25/share/emacs/site-lisp/org-9.7.25/)] Jake
2025-07-22 18:05 ` Ihor Radchenko
2025-08-11 11:04 ` Christian Moe
2025-08-12 6:26 ` Pedro Andres Aranda Gutierrez
2025-08-12 14:26 ` Max Nikulin [this message]
2025-10-19 11:46 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 12:18 Jake
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 \
[email protected] \
[email protected] \
[email protected] \
/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.
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).