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 Date: Wed, 29 Sep 2004 10:54:47 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: "which" command does not expand "~" in path (base-files update needed) Message-ID: <20040929085447.GK14978@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040928194018 DOT GR26145 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20040928194018.GR26145@trixie.casa.cgf.cx> User-Agent: Mutt/1.4.2i On Sep 28 15:40, Christopher Faylor wrote: > On Tue, Sep 28, 2004 at 06:49:44PM +0100, Dave Korn wrote: > > Wonder if this is a real bug then, or if I've misread the shell parsing rules? > >They are a bit ridiculously complicated and full of exceptions and special > >cases..... > > It seems like it's a bug. AFAICT, bash behaves according to its man page: QUOTING [...] Enclosing characters in double quotes preserves the lit­ eral value of all characters within the quotes, with the exception of $, `, and \. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/