Re: tramp and shell, problem on windows 7

[Eli Zaretskii <eliz@gnu.org>]

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: help-gnu-emacs@gnu.org
> Date: Sat, 04 Nov 2017 16:25:43 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > And second, I don't recommend users to set explicit-shell-file-name,
> > as that makes Emacs use a shell that might be different from the one
> > used by the system.  Users who do this should know very well what they
> > are doing, because it could get them in trouble.
> 
> Hmm. The documentation recommends its use, see
> (info "(emacs) Interactive Shell")

That recommendation is for "M-x shell", not for shell-command and its
Dired derivatives.  For "M-x shell", the recommendation makes sense,
because the user should have control on what shell is run in
interactive sessions.  But shell-command is an entirely different
matter.

> And the Tramp manual explains how to set it differently for every remote
> host, see (info "(tramp) Remote processes")
> 
> What else do you recommend on remote systems?

explicit-shell-file-name is not for remote systems.  I was only
talking about setting this for shell-commands executed locally.

> > I think the first question here is why do we see cmdproxy there.  On
> > Windows, shell-file-name is set to cmdproxy, but why does Tramp use
> > that value?
> 
> I could try to dig, if I get traces produced by (setq tramp-verbose 6)
> But this tells only the Tramp part of the story. I suspect, we are faced
> with settings outside Tramp.

You may be right.