From: Ihor Radchenko <email@example.com>
Subject: Re: Error during PDF export but the PDF file is exported
Date: Sun, 16 Oct 2022 10:35:49 +0000 [thread overview]
Message-ID: <87y1tgnji2.fsf@localhost> (raw)
Pascal Quesseveur <firstname.lastname@example.org> writes:
> From time to time I work on files mounted from a remote host which is
> late compared to my pc. Then I encounter errors when producing files
> from Org:
> File xxx wasn't produced
> But the file is produced and is up-to-date. The error message comes
> from org-compile-file. In that function the test is to compare the
> date at the start of function with the date of the produced file. I
> don't know if it's still the case in recent versions, but I think it
> could be changed. For example, instead of using the date at the start
> of the function, we could use the date of the file if it already
> (time (if (file-exists-p output)
> (file-attribute-modification-time (file-attributes output))
> '(0 0 0 0)))
Sorry for the late reply.
This kind of use-case is indeed not considered by our code.
However, your suggestion will only provide a partial fix - when an older
file already exists in the remote folder.
May be there a way to get time on remote server?
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-10-16 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 12:43 Error during PDF export but the PDF file is exported Pascal Quesseveur
2022-10-16 10:35 ` Ihor Radchenko [this message]
[not found] ` <email@example.com>
[not found] ` <871qr6r7op.fsf@localhost>
[not found] ` <firstname.lastname@example.org>
2022-10-19 10:21 ` Ihor Radchenko
2022-10-19 17:24 ` Pascal Quesseveur
2022-10-20 5:12 ` Ihor Radchenko
[not found] ` <email@example.com>
2022-10-21 3:29 ` Ihor Radchenko
2022-10-21 8:05 ` Pascal Quesseveur
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).