From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Strange behaviour on Windows 10
Date: Mon, 30 Sep 2019 12:27:36 +0300 [thread overview]
Message-ID: <83h84ucewn.fsf@gnu.org> (raw)
In-Reply-To: <82tv8uuowv.fsf@gmail.com> (message from Pascal Quesseveur on Mon, 30 Sep 2019 11:14:08 +0200)
> From: Pascal Quesseveur <pquessev@gmail.com>
> Date: Mon, 30 Sep 2019 11:14:08 +0200
>
> >"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>
> EZ> First, did you verify that your Emacs is a 32-bit build? What is the
> EZ> value of system-configuration?
>
> i686-w64-mingw32
OK, that's a 32-bit build, allright.
> EZ> . continue using the 32-bit build, but make a batch file that will
> EZ> call OpenSSH, then put that batch file somewhere on PATH. The
> EZ> batch file should have the same base name as the OpenSSH program
> EZ> you are invoking, probably ssh.cm (this assumes the corresponding
> EZ> Lisp program calls "ssh", not "ssh.exe")
>
> I am not sure it will work. The lisp program calls a script that calls
> ssh. That script is unable to call ssh.exe when it is called from
> emacs.
"Script" meaning what here? a batch file or a Unix shell script? In
the former case, if you put a ssh.cmd on PATH, the script will call it
instead of the missing ssh.exe
> It is definitely better to install a 64 bits version of emacs.
Of course.
next prev parent reply other threads:[~2019-09-30 9:27 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
2019-09-30 9:14 ` Pascal Quesseveur
2019-09-30 9:27 ` Eli Zaretskii [this message]
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=83h84ucewn.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).