X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=2.8 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT X-Spam-Check-By: sourceware.org Date: Wed, 4 Aug 2010 23:22:00 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1994604130.20100804232200@mtu-net.ru> To: "Nellis, Kenneth" , cygwin@cygwin.com Subject: Re: incompatible environment variable names In-Reply-To: <2BF01EB27B56CC478AD6E5A0A28931F20130250E@A1DAL1SWPES19MB.ams.acs-inc.net> References: <2BF01EB27B56CC478AD6E5A0A28931F20130250E@A1DAL1SWPES19MB.ams.acs-inc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Greetings, Nellis, Kenneth! > Well, *somehow* it got into the Cygwin environment, and cygwin.bat directly > invokes bash, so I interpret this as bash creating the Cygwin environment. > Where is the hole in this logic? Even windows itself creates environment variables inaccessible through CMD. Still, they are available to running programs. On another edge, TC(ex. 4NT) shell support variables that not actually environmental, rather - status variables related to current shell state or recently happened events. There's no logic, just usefulness. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 04.08.2010, <23:18> Sorry for my terrible english... -- 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