From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Function to know weither a dir is local or remote
Date: Thu, 20 Oct 2022 19:16:08 +0300 [thread overview]
Message-ID: <834jvyxygn.fsf@gnu.org> (raw)
In-Reply-To: <82sfjimz8v.fsf@gmail.com> (message from Pascal Quesseveur on Thu, 20 Oct 2022 14:54:40 +0200)
> From: Pascal Quesseveur <pquessev@gmail.com>
> Date: Thu, 20 Oct 2022 14:54:40 +0200
>
> My problem is the following. In Org there is a function to create a
> PDF from an org file. That function displays an error message when a
> problem occured during PDF creation. To find out if a problem occured
> during creation, that function compares the time at the beginning of
> the processing and the last modification time of the PDF file. When
> the later is behind the former, the function displays an error
> message. The problem is when the directory of the PDF file is on a
> server, server current time can be different from client current time,
> and then the error can be wrongly displayed.
This problem is not specific to MS-Windows, it is something that Org
should handle on every system. So my first advice is to ask the Org
developers how they propose to fix this problem. The reliance on
synchronized time stamp sounds flaky to me.
> One solution to correct the function can be to create a temporary file
> in the same directory as the PDF file and compare the times using
> creation time of the temporary file instead of local current time. So
> I wanted to know if there exists a function that can check a path and
> tells if its remote or local.
We don't have such a function, no. You could perhaps approximate it
by assuming that every UNC is a remote file.
next prev parent reply other threads:[~2022-10-20 16:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 6:45 Function to know weither a dir is local or remote Pascal Quesseveur
2022-10-20 7:01 ` Eli Zaretskii
2022-10-20 7:27 ` Jean Louis
2022-10-20 8:13 ` Pascal Quesseveur
2022-10-20 8:59 ` Eli Zaretskii
2022-10-20 9:35 ` Pascal Quesseveur
2022-10-20 10:27 ` Eli Zaretskii
2022-10-20 12:54 ` Pascal Quesseveur
2022-10-20 16:16 ` Eli Zaretskii [this message]
2022-10-21 7:46 ` Pascal Quesseveur
2022-10-21 10:45 ` Eli Zaretskii
2022-10-21 17:00 ` tomas
2022-10-25 17:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-25 17:37 ` tomas
2022-10-26 6:41 ` Pascal Quesseveur
2022-10-26 8:25 ` Michael Albinus
2022-10-26 8:59 ` Pascal Quesseveur
2022-10-20 17:39 ` Michael Albinus
2022-10-21 7:47 ` 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834jvyxygn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).