Jim Porter <[email protected]> writes: Hi Jim,
>> Doesn't work. Do you have an idea, which kind of quoting for the remote >> target I need? > > I haven't spent too much time looking at the scp method under MS > Windows, but I know there have been some changes to Win32-OpenSSH that > might affect things here. In v7.9.0.0p1-Beta[1], the quoting logic was > improved (see the "Rich command-line support..." bullet point in the > release notes for details). This might fix the issue you're seeing. Thanks, this looks helpful! > This will probably mean manually installing[2] Win32-OpenSSH, since > Microsoft is very conservative about publishing OpenSSH updates via > their Windows Update service. I haven't tried this yet though, so I > can't be sure if it fixes the issue you're seeing. --8<---------------cut here---------------start------------->8--- ssh -V OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 --8<---------------cut here---------------end--------------->8--- Well, I don't know whether I bite the bullet to support beta versions on MS Windows. I guess I'll just add a comment in tramp-make-copy-program-file-name, and I'll wait until OpenSSH 7.9 is released officially for MS Windows. > v7.9 also includes support for ConPTY (the "Windows Pseudo > Console")[3]. This seems to be relevant mostly for the OpenSSH server, > and might make things work better when connecting to an MS Windows > system; that probably first requires Tramp to handle the ANSI escapes > I mentioned previously, though. Looks also interesting. For the ANSI escape sequences, you might look at tramp-display-escape-sequence-regexp and tramp-device-escape-sequence-regexp and how they are used in tramp-sh.el. They are intended for handling escape sequences emitted by the server; maybe you could do something similar. As said, until I get sshd running on my MS Windows machine, I cannot test myself. > - Jim Best regards, Michael.
