Re: Strange behaviour on Windows 10

[Eli Zaretskii]

> From: Pascal Quesseveur <pquessev@gmail.com>
> Date: Mon, 30 Sep 2019 11:14:08 +0200
> 
> >"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> 
>   EZ> First, did you verify that your Emacs is a 32-bit build?  What is the
>   EZ> value of system-configuration?
> 
> i686-w64-mingw32

OK, that's a 32-bit build, allright.

>   EZ>   . continue using the 32-bit build, but make a batch file that will
>   EZ>     call OpenSSH, then put that batch file somewhere on PATH.  The
>   EZ>     batch file should have the same base name as the OpenSSH program
>   EZ>     you are invoking, probably ssh.cm (this assumes the corresponding
>   EZ>     Lisp program calls "ssh", not "ssh.exe")
> 
> I am not sure it will work. The lisp program calls a script that calls
> ssh. That script is unable to call ssh.exe when it is called from
> emacs.

"Script" meaning what here? a batch file or a Unix shell script?  In
the former case, if you put a ssh.cmd on PATH, the script will call it
instead of the missing ssh.exe

> It is definitely better to install a 64 bits version of emacs.

Of course.