From: Pascal Quesseveur <pquessev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Strange behaviour on Windows 10
Date: Fri, 27 Sep 2019 14:48:41 +0200 [thread overview]
Message-ID: <824l0xoqfq.fsf@gmail.com> (raw)
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.
#+BEGIN_EXAMPLE
>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)
>xtest
OK
OK
#+END_EXAMPLE
and in emacs -Q (version 26.1):
#+BEGIN_EXAMPLE
(defun xtest()
(interactive)
(call-process "xtest" nil t nil))
M-x xtest
OK
NOK
#+END_EXAMPLE
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:
#+BEGIN_EXAMPLE
> 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\;...)
#+END_EXAMPLE
--
Pascal Quesseveur
pquessev@gmail.com
next reply other threads:[~2019-09-27 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 12:48 Pascal Quesseveur [this message]
2019-09-27 13:23 ` Strange behaviour on Windows 10 Eli Zaretskii
2019-09-27 14:15 ` Pascal Quesseveur
2019-09-27 18:26 ` Eli Zaretskii
2019-09-30 9:14 ` Pascal Quesseveur
2019-09-30 9:27 ` Eli Zaretskii
2019-09-30 12:47 ` Pascal Quesseveur
2019-09-30 13:50 ` Eli Zaretskii
2019-09-27 13:45 ` Óscar Fuentes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=824l0xoqfq.fsf@gmail.com \
--to=pquessev@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).