X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=RS1wlBt/PNONaS2m
	6ci0fd2bloBJhamwxzU7WtLf/Q95n9qbzpGMJac6P1Lf0q6OVNjdP6MgtofFfOe4
	HwVQI5/yxrjRckP9L0zG4kEHOp+by/hz3LeaOX740nT0WE0ILgirtpIGa41dB8Ry
	Ivk1v1Htzx8e7wPGqNQ/zmB2pLc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=Nbsyf9M36/lrtaOKdzH2bv
	gxAbI=; b=RjKVOvNMP1pPtY58Osiq714oi962XTxQ5wCFVFkWpvB7Ch986dolSW
	1N0xuXoaH/ZgYMFWNUTQf1Q8JjUKgSGWxW+EMJIJgxTMGK8SovzGxjxxjimKnXoa
	2b4JAjlYWJsYgTy0C8hAwWYMiFrgrsnK+d8FO+A8dL2fkpvNiSY8k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Someone, Repin, enclose, $VAR
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=F5wnTupN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=8_33vRrjMyZ_F0eU408A:9 a=QEXdDO2ut3YA:10
Subject:	Re: Access windows environment variable via cygwin
References:	<29cf87ff-beb3-5c22-eb47-ddb0ad6d4ae0 AT web DOT de> <95bf5921-78ab-c7ac-21a2-0f859e2f6c88 AT SystematicSw DOT ab DOT ca> <1252838367 DOT 20170512152330 AT yandex DOT ru>
To:	cygwin AT cygwin DOT com
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<d143ac26-7c1b-6bd1-b5d4-600259a8af22@SystematicSw.ab.ca>
Date:	Fri, 12 May 2017 07:27:09 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version:	1.0
In-Reply-To:	<1252838367.20170512152330@yandex.ru>
X-CMAE-Envelope:	MS4wfHxAa09FKHJzN92NxTGYZ1H3LDu3JhpqbWvl+/S9cH09f6TfhGVJ/jqpKVaVwM7bU6O7IJqiHu2hOWkGOT1CM2ho2Qi6HvbdSgydGnZCkhJv61bFoHc8 GpSb2P+7c2PHNs1Jhj5q+IKwIwUaYnpFL+e3/XY26UuSgu+ZE8Y4GjXonHYRjdVD1D3iTuxZS7lwRA==
X-IsSubscribed:	yes

On 2017-05-12 06:23, Andrey Repin wrote:
>>> Someone an idea how I could solve this issue?
>> If your scripts use environment variables, they should be careful 
>> to enclose uses of those variables in double quotes "$VAR".
> Correction: You should always use proper quoting, even if you 100% know the
> variable content is "safe", unless the results of not using quoting are
> actually desired.

There's lots of contexts where you don't need quoting, as the shell uses the 
variable and contents and does the right thing, but there is no easy way to 
describe this, other than quote where there are shell parameter expansions, 
which may not mean much to many.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -