[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Strange behaviour on Windows 10

From: Pascal Quesseveur
Subject: Strange behaviour on Windows 10
Date: Fri, 27 Sep 2019 14:48:41 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (windows-nt)


I am encountering a strange problem with emacs on Windows 10 (perhaps
it is not related to emacs but I have not found nothing about it). I
have written a cmd script on Windows 7 which uses plink to launch a
remote command. The script works fine and I use it in emacs through
(call-process) without problems.

As Windows 10 comes with OpenSSH I decided to update my script and use
ssh instead of plink. The script works fine, but it doesn't work
anymore through (call-process). Calls to ssh cause an error:

Le chemin d'accès spécifié est introuvable.

which means the specified filepath cannot be found. ssh.exe is in
C:/Windows/System32/OpenSSH and that directory is in PATH. It seems
that when the script is activated by (call-process) it is unable to
access the C:/Windows/System32/OpenSSH directory. I made the following

>type xtest.cmd
@echo off
if exist "C:\Windows\System32" (echo OK) else (echo NOK)
if exist "C:\Windows\System32\OpenSSH" (echo OK) else (echo NOK)


and in emacs -Q (version 26.1):

(defun xtest()
  (call-process "xtest" nil t nil))
M-x xtest

The problem arises for OpenSHH directory but this is not the only
case. Directory C:\Windows\System32\Microsoft doesn't work either.
The problem is not limited to emacs as I also noted a stange behavior
from which command from EzWin:

> which --version
GNU which v2.20, Copyright (C) 1999 - 2008 Carlo Wood.
(Modified for MS-Windows/MinGW by Eli Zaretskii.)
> which ssh.exe
which: no ssh.exe in (.;C:\Program...;C:\WINDOWS\System32\OpenSSH\;...)

Pascal Quesseveur

reply via email to

[Prev in Thread] Current Thread [Next in Thread]