X-Spam-Check-By: sourceware.org Message-ID: <1139.192.168.0.12.1139733885.squirrel@mail.morrison.mine.nu> In-Reply-To: <20060211204153.GA14065@trixie.casa.cgf.cx> References: <20060210190116 DOT GL14219 AT calimero DOT vinschen DOT de> <2A9FABB3664AF8459CBADA1CE4E402463D1BF1 AT DF-MASTIFF-MSG DOT exchange DOT corp DOT microsoft DOT com> <20060211204153 DOT GA14065 AT trixie DOT casa DOT cgf DOT cx> Date: Sun, 12 Feb 2006 08:44:45 -0000 (GMT) Subject: Re: default PATH From: "John Morrison" To: cygwin AT cygwin DOT com Reply-To: john AT morrison DOT mine DOT nu User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote: > We're > just trying go figure out if removing the ;; translation will affect > many people. We're not looking to add things to the PATH. > > There is a tradeoff here and I don't believe that we really know what > the implications are. You can speculate that thousands of people are > affected by the ;; problem but we haven't had very many complaints about > this and certainly people who are relying on ;; are not going to be > sending email here since Cygwin is working as they expect. > > Also, while skipping empty elements is a trivial operation, it is not > without cost. Every time that we have to guard the user against > something like this, we add another nail to the "cygwin is slow" coffin. Would a reasonable solution would be to make the PATH environment variable a special case and parse it when set? (Appologies if this isn't a reasonable solution) John. -- 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/