GNU bug report logs - #34834
26.1; Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file: Invalid argument, c:/home/ ...

Previous Next

Package: emacs;

Reported by: Jordan Wilson <jordan.t.wilson <at> gmx.com>

Date: Tue, 12 Mar 2019 21:59:02 UTC

Severity: normal

Tags: confirmed

Found in version 26.1

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jordan Wilson <jordan.t.wilson <at> gmx.com>
Subject: bug#34834: closed (Re: bug#34834: 26.1; Remote `eshell/mv' and
 `eshell/cp' on Windows: Opening output file: Invalid argument, c:/home/
 ...)
Date: Sat, 05 Sep 2020 11:32:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#34834: 26.1; Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file: Invalid argument, c:/home/ ...

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 34834 <at> debbugs.gnu.org.

-- 
34834: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34834
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Eli Zaretskii <eliz <at> gnu.org>
To: michael.albinus <at> gmx.de, jordan.t.wilson <at> gmx.com
Cc: 34834-done <at> debbugs.gnu.org
Subject: Re: bug#34834: 26.1;
 Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file:
 Invalid argument, c:/home/ ...
Date: Sat, 05 Sep 2020 14:31:04 +0300
This bug is now solved by changes discussed in bug#26911, and the
solution tested.  So I'm closing this bug.  The solution will be in
Emacs 28.

[Message part 3 (message/rfc822, inline)]
From: Jordan Wilson <jordan.t.wilson <at> gmx.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.1;
 Remote `eshell/mv' and `eshell/cp' on Windows: Opening output file:
 Invalid argument, c:/home/ ...
Date: Tue, 12 Mar 2019 21:54:00 +0000
Hi,
this bug is similar to my previously reported bug #33791. I'm running
Emacs 26.1 (with the patched files.el that fixed that bug[1]) on Windows
10. I've replicated this with "emacs -Q".

When using eshell connected to a GNU/Linux machine, `eshell/cp' and
`eshell/mv' (which are called in eshell with the commands "cp" and "mv")
both return an "Invalid argument" error when the source and destination
are relative paths on the remote machine.

Recipe:
- connect to GNU/Linux machine using plink:
    /plink:jordan <at> domain.com:/home/jordan/
- cp/mv a file between locations on the remote machine
    /plink:jordan <at> domain.com:/home/jordan $ cp file.txt directory/
- returns:
   Opening output file: Invalid argument, c:/plink:jordan <at> domain.com:/home/jordan/file.txt

I'm guessing it's a problem of not correctly handling the relative TRAMP
paths, as it works if provided the full paths for the source and
destination.

Thanks.

Footnotes: 
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33791;msg=34  


In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
 of 2018-05-29 built on TPW550S
Windowing system distributor 'Microsoft Corp.', version 10.0.17134
Recent messages:

Configured using:
 'configure --without-compress-install --without-dbus --with-modules
 'CFLAGS= -O2 -g3''

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND NOTIFY ACL GNUTLS LIBXML2
ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS LCMS2

Important settings:
  value of $LANG: ENG
  locale-coding-system: cp1252

-- 
Jordan Wilson
    Sent from Gnus v5.13, GNU Emacs 26.1



This bug report was last modified 4 years and 341 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.