unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: TRAMP: Problems copying files in emacs-28.0.50 on Windows 10
Date: Mon, 11 Oct 2021 21:49:26 +0200	[thread overview]
Message-ID: <86mtnf1gvt.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <874k9o10ue.fsf@gmx.de> (Michael Albinus's message of "Mon, 11 Oct 2021 09:23:37 +0200")

Hi Michael

Michael Albinus <michael.albinus@gmx.de> writes:
>>> I'm not sure that installed ELPA packages are activated when you run
>>> "emacs -Q". Likely, you must load Tramp in your *scratch* buffer (or you
>>> don't use "-Q" while testing).
>>
>> Please tell me what you mean exactly by loading Tramp in the *scratch*
>> buffer?
>
> I meant adapting the load-path, and requiring Tramp then. However, if
> you have installed the Tramp ELPA package, you can simply call
>
> # emacs -Q -l ~/.emacs.d/elpa/tramp-2.5.1.3/tramp-autoloads

Ah I see now what you meant, thanks for the clarification.  :-)

>> I'll loaded all 20 tramp 2.5.1.3 sources from their Elpa folder and the
>> remote copy operation is working now with emacs -Q. Hurrah!

I jubilated a bit too early in the case of the plinkx method. Even
though it seems to work for config files, for the following archive, of
about 1.4 MB, it failed:

----------------------------------------------------------------------
Tramp: 2.5.1.3
PuTTY: 0.76
GNU Emacs 28.0.50 (build 1, x86_64-w64-mingw32) of 2021-01-15

Copying d:/tmp/tramp/2021-08-11_shard.tar.gz to /plinkx:Prod:/home/vt1/uidg1626/2021-08-11_shard.tar.gz...failed
Copy: ‘d:/tmp/tramp/2021-08-11_shard.tar.gz’ to ‘/plinkx:Prod:/home/vt1/uidg1626/2021-08-11_shard.tar.gz’ failed:
(file-error Writing to process Invalid argument *tramp/plinkx Prod*)

*tramp/plinkx Prod*
FATAL ERROR: Incoming packet was garbled on decryption
----------------------------------------------------------------------

With the (default) pscp method above file transfer is working though.

Let's see how the pscp method'll fare in the long run. :-)

Thanks

    Dieter
    
-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany



  parent reply	other threads:[~2021-10-11 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 20:29 TRAMP: Problems copying files in emacs-28.0.50 on Windows 10 H. Dieter Wilhelm
2021-10-10 16:44 ` Michael Albinus
2021-10-10 18:26   ` [External] : " Drew Adams
2021-10-10 18:29   ` H. Dieter Wilhelm
2021-10-10 19:19     ` Michael Albinus
2021-10-10 20:33       ` H. Dieter Wilhelm
2021-10-11  7:23         ` Michael Albinus
2021-10-11  7:59           ` Michael Albinus
2021-10-11 19:49           ` H. Dieter Wilhelm [this message]
2021-10-12 10:59             ` Michael Albinus
2021-10-12 16:22               ` H. Dieter Wilhelm
2021-10-12 16:33                 ` Michael Albinus
2021-10-12 16:56                   ` H. Dieter Wilhelm
2021-10-12 17:31                     ` Michael Albinus
2021-10-10 23:20       ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-10-11  7:45         ` Michael Albinus

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=86mtnf1gvt.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).