unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Strange behaviour on Windows 10
Date: Fri, 27 Sep 2019 16:23:09 +0300	[thread overview]
Message-ID: <83d0flkh4y.fsf@gnu.org> (raw)
In-Reply-To: <824l0xoqfq.fsf@gmail.com> (message from Pascal Quesseveur on Fri, 27 Sep 2019 14:48:41 +0200)

> From: Pascal Quesseveur <pquessev@gmail.com>
> Date: Fri, 27 Sep 2019 14:48:41 +0200
> 
> #+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

One possible reason is that your Emacs is a 32-bit build.  Windows
silently redirects all accesses to C:\Windows\System32 from 32-bit
programs to C:\Windows\SysWOW64.  If there's no OpenSSH there, you get
an error.

> #+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

This which.exe is a 32-bit program, so it gets the same treatment from
Windows.



  reply	other threads:[~2019-09-27 13:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 12:48 Strange behaviour on Windows 10 Pascal Quesseveur
2019-09-27 13:23 ` Eli Zaretskii [this message]
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=83d0flkh4y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).