emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: pquessev@gmail.com,  emacs-orgmode@gnu.org
Subject: Re: Error during PDF export but the PDF file is exported
Date: Fri, 21 Oct 2022 03:29:26 +0000	[thread overview]
Message-ID: <87a65p7t2h.fsf@localhost> (raw)
In-Reply-To: <98da3e0e-21d1-d342-ae20-5bd9887b668f@gmail.com>

Max Nikulin <manikulin@gmail.com> writes:

> On 20/10/2022 12:12, Ihor Radchenko wrote:
>> What I wanted to say is that
>> `current-time' is good enough if we export to local file.
> Since the patch was not posted to the mailing list, I may be wrong due 
> to some rather wild assumption.
> Paul Eggert convinced me that generally it is a bad idea to compare wall 
> (system) time and file time. They may have different resolution or may 
> have significant offset.  Notice that the following pending patch 
> modifies time handling in `org-compile-file', however I have not tested 
> it for remote files:
> Max Nikulin. [PATCH v2] org-macs.el: Do not compare wall time and file 
> modification time. Sun, 9 Oct 2022 15:18:04 +0700. 
> https://list.orgmode.org/thu03t$16vt$1@ciao.gmane.io
> I am sorry that I did not join to this thread earlier.

You are right, that patch should fix this problem as well.
For some reason, I only remembered that patch as something that concerns
tangling. Now, applied.

Pascal, could you please try the latest main and see if the problem is fixed?

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>

  parent reply	other threads:[~2022-10-21  3:33 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
     [not found]   ` <821qr6n7ue.fsf@gmail.com>
     [not found]     ` <871qr6r7op.fsf@localhost>
     [not found]       ` <82zgdsno6w.fsf@gmail.com>
2022-10-19 10:21         ` Ihor Radchenko
2022-10-19 17:24           ` Pascal Quesseveur
2022-10-20  5:12             ` Ihor Radchenko
     [not found]               ` <98da3e0e-21d1-d342-ae20-5bd9887b668f@gmail.com>
2022-10-21  3:29                 ` Ihor Radchenko [this message]
2022-10-21  8:05                   ` Pascal Quesseveur

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:

  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=87a65p7t2h.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=pquessev@gmail.com \


* 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).