X-Recipient: archive-cygwin@delorie.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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=J1 a6QHRZxfbO6efWJMzJy4pqFjhr2A5EFXk7ANlquRQizvC78RulKOgQksQ1pYSiM3 YWf5XtkvLkoUiL1dYTELSIMwHw/i5vTbIM4xfxQdC2Y3QOn8nekFB6Ba7QQetlen uXrLoFLA+vHTjr5J0xVz75tyrvh4QvUisTzaxpS1s= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=kfIIeP7a v9E1uyO/+w70jSLYARQ=; b=dImKPp1At5xqdIRhzGm9kAbqpnbtZ8Pd97wK+aGM qlcxvRt/k7pP2FTxub7TsKAtzglet4Ea3dhMZz1vcU5ELXyl4FaaTYG0NMGNEfTY 7AZZeRYOfKGGuicblB1YRZcgYWNWTK0whB9zFDZ/731Afmyi3rgkm6/Ll04QHIRo wVM= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-lb0-f179.google.com MIME-Version: 1.0 X-Received: by 10.152.120.201 with SMTP id le9mr1650489lab.68.1392832308206; Wed, 19 Feb 2014 09:51:48 -0800 (PST) In-Reply-To: <5304E874.20906@cygwin.com> References: <1811171498.20140206155616@mtu-net.ru> <5304D694.9090104@cs.umass.edu> <5304E874.20906@cygwin.com> Date: Wed, 19 Feb 2014 18:51:48 +0100 Message-ID: Subject: Re: $PATH contains dot but unclear where it comes from From: Robert Klemme To: cygwin Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes On Wed, Feb 19, 2014 at 6:23 PM, Larry Hall (Cygwin) wrote: > On 2/19/2014 12:16 PM, Robert Klemme wrote: >> The dot is already in the variable before bash even modifies it. > > So that means you need to look in your Windows environment to understand > where this comes from. I did look in windows environment as well (again, see earlier emails). > Don't discount any start-up batch files > (i.e. cygwin.bat), etc., that you may be using to kick-start bash > either. I am using the regular mintty start that cygwin establishes. This is the command line C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico - I can't see in documentation that mintty manipulates the environment in some way. More ideas? robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- 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