From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Demi Obenour <demiobenour@gmail.com>
Cc: 19350@debbugs.gnu.org
Subject: bug#19350: #19350 24.4; Incorrect quoting of %-signs for Windows command shell
Date: Thu, 18 Aug 2016 08:07:41 -0400 [thread overview]
Message-ID: <CAM-tV--KUtM=epj8+R8EW4_BpkMR+z+73MYjNoK-o+NOW8-GoQ@mail.gmail.com> (raw)
In-Reply-To: <CAJEMUN86xBezjzT4_jcE8kfemH=v87Rhf+d0hLwz2u_vTnoVUw@mail.gmail.com>
On Wed, Aug 17, 2016 at 10:02 PM, Demi Obenour <demiobenour@gmail.com> wrote:
> But *nix has no such feature [environment variables affect shell escaping], nor the associated gotcha.
I'm not sure what you're trying to point out here. Why does that
matter? We're talking about Windows, not *nix.
>
>
> On Aug 15, 2016 11:01 AM, "Eli Zaretskii" <eliz@gnu.org> wrote:
>>
>> > From: npostavs@users.sourceforge.net
>> > Date: Sun, 14 Aug 2016 23:13:43 -0400
>> > Cc: 19350@debbugs.gnu.org
>> >
>> > Hmm, maybe we could fix this by making Emacs refuse to apply environment
>> > variables with names ending in carets?
>>
>> I'm very much against disallowing perfectly valid (if rare) use cases
>> just because someone malicious can take advantage of that.
>>
>> From my POV, as long as Emacs itself doesn't produce such shell
>> commands and/or environment variables for any of its features,
>> avoiding this becomes user's responsibility, just like when working at
>> the shell prompt. Of course, if we can find a reliable solution to
>> the problem that doesn't take away features, that'd be better, but
>> failing that, I'm okay with leaving this alone, perhaps documenting
>> somewhere that using % in shell commands when there are environment
>> variables ending in ^ could produce surprising results.
>>
>> Thanks.
next prev parent reply other threads:[~2016-08-18 12:07 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 [this message]
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
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
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='CAM-tV--KUtM=epj8+R8EW4_BpkMR+z+73MYjNoK-o+NOW8-GoQ@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=19350@debbugs.gnu.org \
--cc=demiobenour@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).