GNU bug report logs - #19350
24.4; Incorrect quoting of %-signs for Windows command shell

Previous Next

Full log

Message #41 received at 19350 <at> debbugs.gnu.org (full text, mbox):

From: Demi Obenour <demiobenour <at> gmail.com>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 19350 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#19350: #19350 24.4; Incorrect quoting of %-signs for Windows
 command shell
Date: Thu, 18 Aug 2016 07:54:20 -0400

[Message part 1 (text/plain, inline)]

No, I mean that such environment variables affect shell escaping.

On Aug 17, 2016 10:21 PM, "Noam Postavsky" <npostavs <at> users.sourceforge.net>
wrote:

> On Wed, Aug 17, 2016 at 10:02 PM, Demi Obenour <demiobenour <at> gmail.com>
> wrote:
> > But *nix has no such feature, nor the associated gotcha.
>
> By "feature" you mean having variables whose name ends in a caret (or
> other escape character)? It's true that existing *nix shells don't,
> but the OS does support them (and so hypothetical shells could do as
> well):
>
> (let ((process-environment (cons "ca^=with-caret" process-environment)))
>   (shell-command-to-string "python -c 'import
> os;print(os.environ[\"ca^\"])'")) ;=> "with-caret\n"
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.