Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Re: PATH oddity Date: Thu, 26 May 2005 10:40:00 -0400 Message-ID: <94BF3137C62D3E4CAED7E97F876585F09DA7CC@pauex2ku08.agere.com> From: "Williams, Gerald S \(Jerry\)" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j4QEqLs1014364 Karl M wrote: >>> While looking at my PATH environment variable (in response to the >>> recent postings about sshd and environment variables), I noticed >>> that "." was included. >>> >>> It was caused by a double ; ( a ";;" sequence) in my PATH as >>> defined in the Windows XP My Computer Properties panel. Yitzchak Scott-Thoennes wrote: >> This has been discussed here before; IIRC (and I may not), the . is >> the equivalent of what windows does. An empty entry in the windows >> path (;; in the middle or ; at the beginning or end) makes it search >> the current directory. If that is the meaning under Windows, it would be meaningless in practice since Windows searches the current directory first. However, under bash (and other shells that I'm familiar with) an empty entry is the same as ".". I guess it depends on your POV, but being able to specify the current directory in your Windows PATH, even though it is only meaningful under Cygwin, could be a useful feature. gsw -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/