Re: windows cmd.exe shell

[Michael Albinus]

"Ben Hyde" <address@hidden> writes:

Hi Ben,

> It has, after decades of resistance, become fairly easy[1] to run
> and openssh’s sshd service on window. I’m embarrassed to ask this,
> but does this august gathering have any sage advice about how to
> leverage that via tramp?

Well, I also resist to use MS Windows. From time to time I'm urged to do
it, answering Tramp questions ...

> So far the only thing that works is doing ssh from inside my
> usual M-x shell buffer. That lets me do things, even if it
> messes up the buffer’s rendering by swapping black for white.
> Unsurprisingly dired, visiting files, … don’t work.

Accessing an sshd daemon is only half of the story. After that, Tramp
needs a POSIX compliant shell, and some (UNIX) tools on that remote
machine. In order to initiate this, Tramp calls "/bin/sh".

Likely, that's not the place for a proper shell on MS Windows. If you
know where to find such a shell (a file name), we could try to convince
Tramp to go there.

> My usual trick for unearthing emacs secrets of this kind — code
> search of elisp files on github — isn’t working very well this
> time.

That's the same approach I do - read the sources :-)

> * ben

Best regards, Michael.

PS: Have you tried Tramp's smb method? It accesses MS Windows, out of
the box.