GNU bug report logs - #21562
24.5; Copy dir via Tramp pscp does not work

Previous Next

Full log

Message #17 received at 21562 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Warren Lynn <wrn.lynn <at> gmail.com>
Cc: 21562 <at> debbugs.gnu.org
Subject: Re: bug#21562: 24.5; Copy dir via Tramp pscp does not work
Date: Fri, 02 Oct 2015 19:59:21 +0200

Warren Lynn <wrn.lynn <at> gmail.com> writes:

Hi Warren,

> Actually, things were more broken than I thought. The original code
> did not handle correctly directory copy from local to remote either.
> The reason is function
> tramp-make-copy-program-file-name
> already quotes the target, and then shell-quote-argument quotes the
> target again, so we get double quotes.
>
> I attached a second patch to fix both copying dir from local to
> remote, or remote to local. However, I am not so sure if this is a
> completely correct fix as I don't know much about the "multi-hop"
> thing. Anyway, hope this can serve as a starting point for the
> ultimate proper fix.

Thanks for your investigations.

I've applied your patch to recent Tramp sources, and the Tramp test
suite still passes all expected tests. That's good, but it's with a
local Ubuntu stanza.

Since I don't use MS Windows, I cannot check it for your case. Could
you, please run the test suite, preferred with and without your
patch. You could do this like this (untested):

set REMOTE_TEMPORARY_FILE_DIRECTORY=/pscp:user <at> host:/tmp

"C:\Program Files\emacs-24.5\bin\emacs.exe" -Q -batch -l "C:\Program Files\emacs-24.5\test\automated\tramp-tests.el" -f ert-run-tests-batch-and-exit

Of course, you must adapt some paths in this example.

Since nobody has reported such a problem yet, I suspect that your use
case is not covered yet by the Tramp tests. Could you please describe
exactly, what and how you have tried to copy, especially source and
target paths? I would like to get this problem reproducible. Well, for
this I need to hijack the laptop of my wife :-)

> BTW, all the above works out of box on Emacs 23.3.
>
> To be honest, I am quite disappointed with Emacs recent (last 2 or 3
> years) release quality. Seems some convoluted low-quality code was
> checked in the first place, and then not enough testing was done
> before release. Don't know if I have any right to complain in the
> first place as I am not an active developer here. But I would hate to
> see my favorite editor Emacs going down this path further.

I cannot speak for Emacs in general. But none of the Tramp contributors
uses MS Windows locally, as far as I am aware of. If there won't be any
volunteer for testing this, we cannot expect a better quality.

Additionally, the Tramp tests on MS Windows require special settings
(see %REMOTE_TEMPORARY_FILE_DIRECTORY% I've shown above). I have no idea
how we could establish a mockup Tramp connection method for testing, as
we have done it for local unixoid systems.

Best regards, Michael.

PS: Starting on Monday, I'll be offline for about a week.

Previous Next

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