From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
37576@debbugs.gnu.org
Subject: bug#37576: 27.0.50; [Windows] "Permission denied" error from call-process if executable not found
Date: Wed, 2 Oct 2019 18:09:14 +0100 [thread overview]
Message-ID: <CAPM58oj9jXnhEw0NSJ1bOZkSVc9Cqqa1QZeS0PbkKNtf-3dEgQ@mail.gmail.com> (raw)
In-Reply-To: <838sq3856a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Wed, 2 Oct 2019 at 17:48, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Andreas Schwab <schwab@linux-m68k.org>
> > Date: Wed, 02 Oct 2019 13:02:43 +0200
> > Cc: Richard Copley <rcopley@gmail.com>, 37576@debbugs.gnu.org
> >
> > On Okt 02 2019, Juanma Barranquero <lekktu@gmail.com> wrote:
> >
> > > When the search fails, Emacs is now reporting "permission denied" if
> some
> > > PATH element was non-existent, or "no such file or directory"
> otherwise. At
> > > least on Windows.
> >
> > And that is a bug. A PATH element pointing to a non-existing directory
> > should be ignored.
>
> I don't know what "ignore" means in this case, since call-process
> should signal an error if it's unable to find the program. If you
> mean that nonexistent directories should be treated as if they
> existed, but didn't have the program in them, then I agree, and I've
> now fixed the Windows build's behavior to match that of the Posix
> builds in this case.
>
I agree with that too, FWIW. Thanks.
> I still didn't hear from Richard confirming that his case is indeed
> caused by a non-existent directory on PATH.
Yes it is. (At least, there *are* non-existent directories in PATH, and I
get the correct message now.)
Maybe there are other
> factors at work here.
>
[-- Attachment #2: Type: text/html, Size: 2350 bytes --]
next prev parent reply other threads:[~2019-10-02 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 19:43 bug#37576: 27.0.50; [Windows] "Permission denied" error from call-process if executable not found Richard Copley
2019-10-01 20:43 ` Juanma Barranquero
2019-10-01 22:05 ` Richard Copley
2019-10-01 22:16 ` Juanma Barranquero
2019-10-01 22:28 ` Richard Copley
2019-10-01 22:33 ` Juanma Barranquero
2019-10-01 22:40 ` Richard Copley
2019-10-01 23:55 ` Juanma Barranquero
2019-10-02 10:07 ` Andreas Schwab
2019-10-02 10:18 ` Juanma Barranquero
2019-10-02 11:02 ` Andreas Schwab
2019-10-02 11:47 ` Juanma Barranquero
2019-10-02 12:58 ` Andreas Schwab
2019-10-02 13:17 ` Juanma Barranquero
2019-10-02 16:48 ` Eli Zaretskii
2019-10-02 17:09 ` Richard Copley [this message]
2019-10-02 17:19 ` Eli Zaretskii
2019-10-02 9:21 ` Lars Ingebrigtsen
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=CAPM58oj9jXnhEw0NSJ1bOZkSVc9Cqqa1QZeS0PbkKNtf-3dEgQ@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=37576@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
--cc=schwab@linux-m68k.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).