[Top][All Lists]

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

Re: Strange behaviour on Windows 10

From: Óscar Fuentes
Subject: Re: Strange behaviour on Windows 10
Date: Fri, 27 Sep 2019 15:45:06 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Pascal Quesseveur <> writes:

> Hello,
> 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
> test.
>>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)
> OK
> OK
> and in emacs -Q (version 26.1):
> (defun xtest()
>   (interactive)
>   (call-process "xtest" nil t nil))
> M-x xtest
> OK
> 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\;...)

Cannot reproduce the problem here with your xtest.cmd.

Probably a permissions problem. I only know the basics about Windows
access control, but maybe your Emacs executable has some attribute that
restricts the files it can see.

Can you navigate with Dired to the OpenSSH directory? If you execute
emacs.exe as Administrator, the problem persists?

reply via email to

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