From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jordan.t.wilson@gmx.com, 34834@debbugs.gnu.org
Subject: bug#34834: 26.1; Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file: Invalid argument, c:/home/ ...
Date: Fri, 29 Mar 2019 14:24:28 +0100 [thread overview]
Message-ID: <87k1ghreyb.fsf@gmx.de> (raw)
In-Reply-To: <834l7lkga1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Mar 2019 15:37:42 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
> IIUC, it works on Posix platforms by sheer luck, is that right?
Yes.
> IOW, on Posix platforms, we also don't recognize this is a remote file
> name until it's too late, and we only get away because the file name
> starts with a slash, and so looks like an absolute file name on Posix
> platforms. is that correct?
Yes.
I will extend tramp-tests.el to test expand-file-name also with a
relative DIR argument. At least when running on Windows platforms, this
shall trigger this error (and prove it is corrected, when it is
corrected).
> And thanks for the detailed description of the traces.
Best regards, Michael.
next prev parent reply other threads:[~2019-03-29 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:54 bug#34834: 26.1; Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file: Invalid argument, c:/home/ Jordan Wilson
2019-03-28 17:44 ` Michael Albinus
2019-03-28 17:52 ` Eli Zaretskii
2019-03-28 17:57 ` Michael Albinus
2019-03-28 19:29 ` Eli Zaretskii
2019-03-29 11:16 ` Michael Albinus
2019-03-29 12:37 ` Eli Zaretskii
2019-03-29 13:24 ` Michael Albinus [this message]
2019-03-29 14:12 ` Eli Zaretskii
2019-03-29 16:02 ` Michael Albinus
2019-03-29 17:46 ` Eli Zaretskii
2020-09-01 15:59 ` Eli Zaretskii
2020-09-05 11:31 ` Eli Zaretskii
2020-08-26 22:46 ` Paul Eggert
2020-08-27 13:28 ` Paul Eggert
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=87k1ghreyb.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=34834@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jordan.t.wilson@gmx.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.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).