unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Demi Obenour <demiobenour@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 19350@debbugs.gnu.org
Subject: bug#19350: #19350 24.4; Incorrect quoting of %-signs for Windows command shell
Date: Thu, 18 Aug 2016 07:54:20 -0400	[thread overview]
Message-ID: <CAJEMUN-y+XU8NK9pGW5erb1JO2=oPfN-_9qPXJCG9Eh6De7bKw@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-_iJWZo7taGYMUf9w9+n4k70P09mUMi3iGT2q8B8bpvxA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

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

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

> On Wed, Aug 17, 2016 at 10:02 PM, Demi Obenour <demiobenour@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"
>

[-- Attachment #2: Type: text/html, Size: 1147 bytes --]

  reply	other threads:[~2016-08-18 11:54 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 [this message]
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
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='CAJEMUN-y+XU8NK9pGW5erb1JO2=oPfN-_9qPXJCG9Eh6De7bKw@mail.gmail.com' \
    --to=demiobenour@gmail.com \
    --cc=19350@debbugs.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 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).