From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36270@debbugs.gnu.org
Subject: bug#36270: executable-find does not find shell commands on MSYS2
Date: Wed, 19 Jun 2019 21:20:30 +0200 [thread overview]
Message-ID: <CAAeL0STQEsc9JeBmPBhOn9vdjpXfSGXTHNVAaH6AcoT5Bnm8gQ@mail.gmail.com> (raw)
In-Reply-To: <83o92tr1b2.fsf@gnu.org>
On Wed, Jun 19, 2019 at 6:24 PM Eli Zaretskii <eliz@gnu.org> wrote:
> Kids down here have a saying: "almost doesn't count" ;-)
Err... Don't want to think about the context for *that* ;-)
> Exactly. So what would be the point of having a general-purpose API
> return files that can be useful only with some methods of running a
> program? It will only cause confusion and bug reports.
That's an argument about the general-purpose API return these files,
not about having a special-purpose API, isn't it?
> So to support that, we will need to change sys_spawnve and/or
> cmdproxy to detect an extension that appears in PATHEXT, and then
> either invoke through cmdproxy or use ShellExecute instead of
> CreateProcess. And this is the more complex part of the job.
Ok, now I understand. I will look into it, but no promises and of
course no hurry.
> One non-ugly fix is to use RCS from the ezwinports site. The binaries
> there are 32-bit, but I don't think it will make any difference.
With your binaries installed the test will pass (haven't tested yet,
but seems likely). But that does not solve the issue that someone with
a MSYS2 build environment has a working rcs installation, and yet the
vc-tests fail. Of course, the thing is that, from Emacs POV, that's
not a "working rcs installation" at all...
prev parent reply other threads:[~2019-06-19 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 23:42 bug#36270: executable-find does not find shell commands on MSYS2 Juanma Barranquero
2019-06-18 0:23 ` Glenn Morris
2019-06-18 0:57 ` Juanma Barranquero
2019-06-18 16:51 ` Eli Zaretskii
2019-06-18 20:49 ` Juanma Barranquero
2019-06-19 16:24 ` Eli Zaretskii
2019-06-19 17:38 ` Andy Moreton
2019-06-19 19:22 ` Juanma Barranquero
2019-06-19 19:20 ` Juanma Barranquero [this message]
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=CAAeL0STQEsc9JeBmPBhOn9vdjpXfSGXTHNVAaH6AcoT5Bnm8gQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=36270@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).