From: Pascal Quesseveur <pquessev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Function to know weither a dir is local or remote
Date: Fri, 21 Oct 2022 09:46:47 +0200 [thread overview]
Message-ID: <82o7u5r53s.fsf@gmail.com> (raw)
In-Reply-To: <834jvyxygn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Oct 2022 19:16:08 +0300")
>"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> This problem is not specific to MS-Windows, it is something that
EZ> Org should handle on every system.
Yes, I never said it was specific to MS-Windows.
EZ> So my first advice is to ask the Org developers how they propose
EZ> to fix this problem. The reliance on synchronized time stamp
EZ> sounds flaky to me.
I did that. I was trying to find a solution to improve the function.
EZ> We don't have such a function, no.
file-remote-p works only when you use a special file name syntax. This
is not clear from the docstring.
EZ> You could perhaps approximate it by assuming that every UNC is a
EZ> remote file.
But as you said every UNC is not a remote file.
--
Pascal Quesseveur
pquessev@gmail.com
next prev parent reply other threads:[~2022-10-21 7:46 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
2022-10-21 7:46 ` Pascal Quesseveur [this message]
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=82o7u5r53s.fsf@gmail.com \
--to=pquessev@gmail.com \
--cc=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).