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 From: "Dave Korn" To: Subject: RE: "which" command does not expand "~" in path (base-files update needed) Date: Wed, 29 Sep 2004 12:19:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20040929085447.GK14978@cygbert.vinschen.de> Message-ID: X-OriginalArrivalTime: 29 Sep 2004 11:19:14.0720 (UTC) FILETIME=[2702C200:01C4A616] > -----Original Message----- > From: cygwin-owner On Behalf Of Corinna Vinschen > Sent: 29 September 2004 09:55 > 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 \. > Well, yeh, but, like, y'know, the tilde was _outside_ the quotes. YMKMC! :) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/