X-Spam-Check-By: sourceware.org Date: Sun, 12 Feb 2006 13:03:18 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: default PATH Message-ID: <20060212120318.GS14219@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <021120062022 DOT 25491 DOT 43EE478C000D242F0000639322007456720A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <021120062022.25491.43EE478C000D242F0000639322007456720A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.4.2i 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 On Feb 11 20:22, Eric Blake wrote: > I strongly oppose option 3 - cygwin should never add '.' implicitly to the > front of a POSIX path - if you are crazy enough to want dot there, put > it there yourself explicitly. But I like option 2, of squeezing ';;' into a > single ':' (avoiding the implicit dot of $PATH '::'), and ignoring trailing ';' > (again, avoiding the implicit dot of $PATH trailing ':'). If the user wants > dot in the middle or at the end, automagically converted from > the Windows %PATH%, then they can explicitly use ';.;' or trailing > ';.' to make their intent clear. And since Windows always implicitly > prepends '.' to %PATH%, this might cut down on the traffic to this > list of "how did . get on my $PATH?". (Although it will probably > increase the traffic of "why did ;; get turned into : instead of ::?") That's unavoidable. Whatever you do, somebody will complain. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/