From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18745@debbugs.gnu.org
Subject: bug#18745:
Date: Thu, 29 Oct 2015 18:22:57 +0100 [thread overview]
Message-ID: <CAAeL0STTTu42U-vKHs7wb4c33sJi3sAMwSju0aQQs_RdR6o6Vw@mail.gmail.com> (raw)
In-Reply-To: <834mh93az4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Thu, Oct 29, 2015 at 5:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> The CreateProcess deficiency we test there has nothing to do with
> trailing whitespace, btw.
That's what I meant: that changing the test to accommodate for a TCC
incompatibility still would make sense because the trailing space is not
what the test is about. Only I said it with less words and zero clarity.
> Anyway, does it work to put "ComSpec=%windir%\system32\cmd.exe" into
> process-environment before running that code?
No. I had already tried that, and now I've done some more checking. (In all
cases, I run the test from the shell with emacs -batch -l ert -l
process-test [etc]).
- Testing from CMD.EXE works (as expected)
- Setting COMSPEC to point to CMD and testing from TCC.EXE also works.
- let-binding process-environment to (cons
"ComSpec=C:\\windows\\system32\\cmd.exe" process-environment) around the
test does not work.
- Using (setenv "ComSpec" "C:\\Windows\\system32\\cmd.exe") or (setenv
"ComSpec" "%windir%\\system32\\cmd.exe" t) in the test function before
calling call-process does not work
- Same for variants with forward slashes, %windir% vs. explicit path, etc.
I would be very surprised that the process-environment does not affect
call-process, so I *must* be missing something obvious. I'll take a closer
look as soon as I have a little more time.
J
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next prev parent reply other threads:[~2015-10-29 17:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 4:33 bug#18745: 24.3; MS Windows, `call-process-shell-command' fails on `shell-quote-argument'ed bat file with quoted args Noam Postavsky
2014-10-16 6:50 ` Eli Zaretskii
2014-10-16 13:47 ` Stefan Monnier
2014-10-16 13:57 ` Eli Zaretskii
2014-10-16 16:28 ` Noam Postavsky
2014-10-16 17:06 ` Eli Zaretskii
2014-10-16 21:30 ` Noam Postavsky
2014-10-22 1:12 ` Noam Postavsky
2014-10-22 17:12 ` Eli Zaretskii
2014-10-23 1:33 ` Noam Postavsky
2014-10-23 15:52 ` Eli Zaretskii
2014-10-25 9:16 ` Eli Zaretskii
2014-10-25 14:03 ` Noam Postavsky
2014-10-16 20:15 ` Stefan Monnier
2014-10-16 21:50 ` Noam Postavsky
2014-10-17 0:38 ` Stefan Monnier
2014-10-17 6:10 ` Eli Zaretskii
2014-10-17 6:05 ` Eli Zaretskii
2015-10-27 11:49 ` bug#18745: Juanma Barranquero
2015-10-27 19:14 ` bug#18745: Eli Zaretskii
2015-10-27 23:24 ` bug#18745: Juanma Barranquero
2015-10-28 16:01 ` bug#18745: Eli Zaretskii
2015-10-29 3:38 ` bug#18745: Juanma Barranquero
2015-10-29 16:17 ` bug#18745: Eli Zaretskii
2015-10-29 17:22 ` Juanma Barranquero [this message]
2015-10-30 14:25 ` bug#18745: Juanma Barranquero
2015-10-30 14:55 ` bug#18745: Eli Zaretskii
2015-10-30 17:09 ` bug#18745: Juanma Barranquero
2015-10-30 20:10 ` bug#18745: Eli Zaretskii
2015-10-31 23:20 ` bug#18745: Juanma Barranquero
2015-11-01 17:49 ` bug#18745: Eli Zaretskii
2015-11-01 18:29 ` bug#18745: Juanma Barranquero
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=CAAeL0STTTu42U-vKHs7wb4c33sJi3sAMwSju0aQQs_RdR6o6Vw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=18745@debbugs.gnu.org \
--cc=eliz@gnu.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).