From: Ihor Radchenko <yantar92@posteo.net>
To: pquessev@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Error during PDF export but the PDF file is exported
Date: Thu, 20 Oct 2022 05:12:39 +0000 [thread overview]
Message-ID: <871qr39iyg.fsf@localhost> (raw)
In-Reply-To: <82lepbohfc.fsf@gmail.com>
Pascal Quesseveur <pquessev@gmail.com> writes:
>>"IR" == Ihor Radchenko <yantar92@posteo.net> writes:
>
> IR> I think that creating a temporary file locally is excessive.
>
> Perhaps, but I couldn't find another way.
I think we are miscommunication. What I wanted to say is that
`current-time' is good enough if we export to local file. The whole
route with creating temporary file and getting its attributes is only
needed in remote directory.
> IR> You could guard the logic behind `file-remote-p'.
>
> FMU file-remote-p works onnly when there is a handler on path for
> operation file-remote-p, which is not true in the general
> case. Otherwise that function returns nil.
If file-remote-p does not work, I doubt that we can export to that
directory at all.
> OTOH it is possible to reserve the creation of a temporary file only
> when the file is not already present.
It is also an option.
--
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-20 5:12 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 [this message]
[not found] ` <98da3e0e-21d1-d342-ae20-5bd9887b668f@gmail.com>
2022-10-21 3:29 ` Ihor Radchenko
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:
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=871qr39iyg.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=pquessev@gmail.com \
/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).