From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Strange behaviour on Windows 10
Date: Fri, 27 Sep 2019 21:26:05 +0300 [thread overview]
Message-ID: <83sgohiojm.fsf@gnu.org> (raw)
In-Reply-To: <82r241n7uf.fsf@gmail.com> (message from Pascal Quesseveur on Fri, 27 Sep 2019 16:15:36 +0200)
> From: Pascal Quesseveur <pquessev@gmail.com>
> Date: Fri, 27 Sep 2019 16:15:36 +0200
>
> >"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>
> EZ> One possible reason is that your Emacs is a 32-bit build. Windows
> EZ> silently redirects all accesses to C:\Windows\System32 from 32-bit
> EZ> programs to C:\Windows\SysWOW64. If there's no OpenSSH there, you get
> EZ> an error.
>
> Thank you. Yes, there is no OpenSSH dir in SysWOW64. I totally forgot
> about 32/64 bits problems.
>
> Does that mean I have to install a 64 bits emacs to make it work?
First, did you verify that your Emacs is a 32-bit build? What is the
value of system-configuration?
If that indeed indicates a 32-bit build, you have 2 alternatives:
. install a 64-bit build of Emacs (this is the preferred solution,
and will serve you better down the road)
. continue using the 32-bit build, but make a batch file that will
call OpenSSH, then put that batch file somewhere on PATH. The
batch file should have the same base name as the OpenSSH program
you are invoking, probably ssh.cm (this assumes the corresponding
Lisp program calls "ssh", not "ssh.exe")
next prev parent reply other threads:[~2019-09-27 18:26 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
2019-09-27 14:15 ` Pascal Quesseveur
2019-09-27 18:26 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sgohiojm.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.