From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33016@debbugs.gnu.org, bauer.klaus.dieter@gmail.com
Subject: bug#33016: 26.1; (make-process ...) doesn't signal an error, when executable given as absolute Windows path does not exist
Date: Thu, 11 Apr 2019 20:55:33 +0300 [thread overview]
Message-ID: <83mukw4eay.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9TsiGBVEPCxHX4FJP1aNTU4PAXcUc6a5fMmZH8SWqsrw@mail.gmail.com> (message from Noam Postavsky on Thu, 11 Apr 2019 13:34:25 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Thu, 11 Apr 2019 13:34:25 -0400
> Cc: Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com>, 33016@debbugs.gnu.org
>
> > Doesn't it work to simply set its value before the second test?
>
> Yes, or in each test, since the tests don't necessarily have knowledge
> of what order they're called in (I think it's currently alphabetical
> order of test name). See attached diff (against the state of my v3
> patch), but it seems a bit silly to make the variable Lisp accessible
> just for this obscure test case. I don't see any other way though.
OK. That diff includes some unrelated stuff, though -- you didn't
mean to install it as is, right?
next prev parent reply other threads:[~2019-04-11 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 12:55 bug#33016: 26.1; (make-process ...) doesn't signal an error, when executable given as absolute Windows path does not exist Klaus-Dieter Bauer
2018-10-11 14:22 ` Eli Zaretskii
2018-10-19 8:03 ` Klaus-Dieter Bauer
2018-10-19 8:30 ` Eli Zaretskii
2019-04-08 18:34 ` Noam Postavsky
2019-04-08 18:58 ` Eli Zaretskii
2019-04-09 14:13 ` Noam Postavsky
2019-04-09 14:33 ` Eli Zaretskii
2019-04-10 21:58 ` Noam Postavsky
2019-04-11 14:04 ` Eli Zaretskii
2019-04-11 17:34 ` Noam Postavsky
2019-04-11 17:55 ` Eli Zaretskii [this message]
2019-04-12 0:44 ` Noam Postavsky
2019-04-12 8:44 ` Eli Zaretskii
2019-04-12 18:20 ` Noam Postavsky
2019-04-12 18:44 ` Eli Zaretskii
2019-04-15 12:21 ` Noam Postavsky
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=83mukw4eay.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33016@debbugs.gnu.org \
--cc=bauer.klaus.dieter@gmail.com \
--cc=npostavs@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 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.