unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 37576@debbugs.gnu.org
Subject: bug#37576: 27.0.50; [Windows] "Permission denied" error from call-process if executable not found
Date: Tue, 1 Oct 2019 23:05:34 +0100	[thread overview]
Message-ID: <CAPM58ogzpPfK0O51EGr3LVNVN2eSGv3EWN14ujRhhoavn_erBQ@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0STJw3SywMfYw6ekTCggnGTt-5FQySvFWa0wMa0g_T2xcQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

On Tue, 1 Oct 2019 at 21:43, Juanma Barranquero <lekktu@gmail.com> wrote:

> On Tue, Oct 1, 2019 at 9:56 PM Richard Copley <rcopley@gmail.com> wrote:
>
> > In "emacs -Q", if the file "xyzzy" does not exist on the path,
> (call-process "xyzzy") now leaves this in the *Messages* buffer:
> >
> >   forward-sexp: Searching for program: Permission denied, xyzzy
> >
> > In older versions the entry in the message buffer is a true statement:
> >
> >   eval: Searching for program: No such file or directory, xyzzy
>
> In the current trunk, I get "No such file on directory".
>
> ELISP> (call-process "xyzzy")
> *** Eval error ***  Searching for program: No such file or directory, xyzzy
>
> > Repository revision: cbc507779b8f56ce0abf596416e8e3847de88e10
> > Repository branch: buster
>
> After Paul changes adding more strict file checking, there were some fixes
> to ease up. Perhaps you got a revision in between. I cannot say, because
> the repository revision of your report is likely some local change by you
> (it's not in the public repository).
>

I get the same results in "emacs -Q" rebuilt from scratch from current
pristine master, 2698d3dba2 (2019-10-01 23:15:03 2019 +0300). After
building and running using this command...:

  git reset --hard 2698d3db && git clean -xfd && ./autogen.sh &&
./configure && make && src/emacs.exe -Q

...the recipe below pops up the Lisp debugger.

M-: (call-process SPC "xyzzy") RET
c ;; debugger-continue

On continuing in the debugger, it prints "forward-sexp: Searching for
program: Permission denied, xyzzy" in the *Messages* buffer.

[-- Attachment #2: Type: text/html, Size: 2378 bytes --]

  reply	other threads:[~2019-10-01 22:05 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 [this message]
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
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=CAPM58ogzpPfK0O51EGr3LVNVN2eSGv3EWN14ujRhhoavn_erBQ@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=37576@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /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).