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:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=J0EI0/H0FPHkbmA2
	mbE5ntdXQxR+Q254oNlx2eFyyr45KPq5mj8UyFSA3U72KUNoBT6B9+huZ1qILe8n
	MX6ER6hkMWfgY4C7j7q9OyDdfOnj+SrAQWAv9+4qkzR37ZigICGY7yZ/uFD/1Cjc
	/3f5O9D6FF1mfj/FhioK2DNN3os=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Retrieving per-process environment block?
To: cygwin@cygwin.com
References: <CAOTD34ZFH5E3r3AuDOXctss46e1hoU2f9pwE1mt4L674J2Ak_A@mail.gmail.com> <20161117140012.GA23664@calimero.vinschen.de> <CAOTD34Y9TRq2Qq8Mn2awTf9SCgz0qnbBa-a117pkSEvz9gaHKQ@mail.gmail.com> <98eb08bf-5012-fe14-b10c-241b427c4366@cs.umass.edu> <CAOTD34bPTUkKiHSmqvczz6juePBD=6PyzabDFfHpYL_cFzyf9A@mail.gmail.com> <2925977.20161129192741@yandex.ru> <583E1D4A.4020703@gmx.de> <111bc961-5f69-8e27-f78a-2b82f351d811@cs.umass.edu>
From: Peter Rosin <peda@lysator.liu.se>
Message-ID: <237e4e33-4b51-a124-4108-d67e715dcbf0@lysator.liu.se>
Date: Wed, 30 Nov 2016 10:15:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <111bc961-5f69-8e27-f78a-2b82f351d811@cs.umass.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

On 2016-11-30 04:00, Eliot Moss wrote:
> On 11/29/2016 7:28 PM, Herbert Stocker wrote:
> 
>> Or we simply copy the variables unconverted to the Windows environment
>> block, as the Windows env block is not used for anything else - up to
>> now it is not updated at all.
> 
> Maybe we could stash them inside one large variable?  Would that help
> at all?  (It does demand a quoting convention, but since this is all
> internal stuff, that may not be too hard.)

I believe this is a dead end. The Windows environment block has an
unacceptable size limit which is circumvented by the internal Cygwin
handling. Since this is about exposing said Cygwin environment, it
would simply not work for big environments.

Cheers,
Peter

--
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