X-Spam-Check-By: sourceware.org Message-ID: <908c474e0602080158v2f84c0agb63e7ddcf5443d72@mail.gmail.com> Date: Wed, 8 Feb 2006 10:58:32 +0100 From: Julien Thewys Reply-To: jt AT udev DOT org To: Eric Blake Subject: Re: default PATH Cc: cygwin AT cygwin DOT com In-Reply-To: <020620061512.1594.43E767490006AAD30000063A22007507840A050E040D0C079D0A@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline References: <020620061512 DOT 1594 DOT 43E767490006AAD30000063A22007507840A050E040D0C079D0A AT comcast DOT net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id k19IGh2B001512 Solution is to reinstall 'base-files' (seehttp://www.cygwin.com/ml/cygwin/2006-02/msg00222.html). My PATH was appended with '.' because of a trailing ';' in my Windows PATH. Thank you.--jt On 2/6/06, Eric Blake wrote:> > I upgrade to 1.5.19-4 and my default PATH has changed:> >> > PATH is "inherited" from my WinXP environment as usual but it is not> > prepend with "/bin" like before the upgrade, and is now appended with> > ".".> > I cannot find where this happen (my .bashrc is unchanged).>> Try opening a cmd.com window in c:\cygwin\bin (or whatever> it is named), then running 'bash --login -xv' to see every command> executed by bash during startup. Maybe that will help you> pinpoint the culprit.>> >> > Also, when I start cygwin (shell in rxvt), it throws me in "/usr/bin"> > (which is a mount of "/bin") instead of my usual "~/".>> Sounds like it might be a problem with $HOME, such that> bash does not know where to find your ~/.bashrc.>> >> > I can fix all this by hand in my .bashrc but I want to have a clean> > fix (avoid cygwin to do the bad job at the first place).> > Can someone tell me where to look at?> >> > Note: the upgrade also updated coreutils, readline and other minor stuff.>> Perhaps you also upgraded base-files, and maybe something> in there was the culprit?>> Hint: following these directions is a great help to debugging:> > Problem reports: http://cygwin.com/problems.html>> --> Eric Blake> volunteer cygwin bash maintainer> --Julien