From: Juanma Barranquero <lekktu@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Richard Copley <rcopley@gmail.com>, 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 13:47:28 +0200 [thread overview]
Message-ID: <CAAeL0SQKztfW_rDZpvCt9gat-egFMc3=7RHgcxT3Cue0h23eyg@mail.gmail.com> (raw)
In-Reply-To: <875zl79zqk.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Wed, Oct 2, 2019 at 1:02 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
> And that is a bug. A PATH element pointing to a non-existing directory
> should be ignored.
Just out of curiosity... Says who? I mean, there's a standard (POSIX or
whatever) that says what kind of error message you should give when
searching the PATH and not finding what you were looking for? Or it just
states that non-existing elements should be ignored, in the sense of not
stopping the search?
Not arguing, genuinely curious.
[-- Attachment #2: Type: text/html, Size: 641 bytes --]
next prev parent reply other threads:[~2019-10-02 11:47 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SQKztfW_rDZpvCt9gat-egFMc3=7RHgcxT3Cue0h23eyg@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=37576@debbugs.gnu.org \
--cc=rcopley@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 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.