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 15:17:28 +0200 [thread overview]
Message-ID: <CAAeL0ST3vABT2f7iZV=tYYGsTdr-3=8cQMV80_Oj=HUoEczjYQ@mail.gmail.com> (raw)
In-Reply-To: <871rvv9udg.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
> That's how the shell behaves.
Ok.
In this specific case, which is trying to run a program and failing from
inside Emacs, I think it could be argued both ways: that it is more
informative to know there's something a bit off in your PATH, or that it is
irrelevant, because the relevant info is that the program couldn't be run.
I suppose the answer to "one way or the other" is "Yes, as long as it is
consistently done in all platforms."
[-- Attachment #2: Type: text/html, Size: 560 bytes --]
next prev parent reply other threads:[~2019-10-02 13:17 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 [this message]
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='CAAeL0ST3vABT2f7iZV=tYYGsTdr-3=8cQMV80_Oj=HUoEczjYQ@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.