From: Demi Obenour <demiobenour@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19350@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#19350: #19350 24.4; Incorrect quoting of %-signs for Windows command shell
Date: Mon, 3 Oct 2016 15:38:52 -0400 [thread overview]
Message-ID: <CAJEMUN8+c9fjQmKWj8_h6aQ1jwo=2yebbnQuAi9wn=0QjiOaFg@mail.gmail.com> (raw)
In-Reply-To: <CAJEMUN9xcizd9rNYiZueg4gjRAcPxh4V_JZdaSt5jr-P4LRe-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
I think we can assume that it will keep working in future versions of
cmd.exe, as MS won't break backwards compatibility here, and it seems to be
a consequence of documented parsing rules.
But yes, it would be great to just skip the shell. I don't think we should
replace it either. Lisp should always pass an argument list when creating
a process.
[-- Attachment #2: Type: text/html, Size: 397 bytes --]
next prev parent reply other threads:[~2016-10-03 19:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 18:43 bug#19350: 24.4; Incorrect quoting of %-signs for Windows command shell Demetrios Obenour
2016-08-10 13:00 ` bug#19350: #19350 " Noam Postavsky
2016-08-10 16:11 ` Eli Zaretskii
2016-08-11 23:11 ` Demi Obenour
2016-08-12 0:41 ` npostavs
[not found] ` <CAJEMUN_nkRgwCF7h03x=_jdHDLGqC+DBk0=3NNJhZTx5woW8gg@mail.gmail.com>
[not found] ` <CAJEMUN-HMMJu1FTDrKEmn_8nOaMhDeE8Te2JuE7jVdvuqLtbNQ@mail.gmail.com>
2016-08-15 0:44 ` Demi Obenour
2016-08-15 3:13 ` npostavs
2016-08-15 15:01 ` Eli Zaretskii
2016-08-18 2:02 ` Demi Obenour
2016-08-18 2:21 ` Noam Postavsky
2016-08-18 11:54 ` Demi Obenour
2016-08-18 12:07 ` Noam Postavsky
2016-08-18 14:17 ` Eli Zaretskii
2016-10-03 18:47 ` Noam Postavsky
2016-10-03 19:15 ` Eli Zaretskii
[not found] ` <CAJEMUN9xcizd9rNYiZueg4gjRAcPxh4V_JZdaSt5jr-P4LRe-A@mail.gmail.com>
2016-10-03 19:38 ` Demi Obenour [this message]
2018-02-09 0:17 ` 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='CAJEMUN8+c9fjQmKWj8_h6aQ1jwo=2yebbnQuAi9wn=0QjiOaFg@mail.gmail.com' \
--to=demiobenour@gmail.com \
--cc=19350@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.