Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <6.1.2.0.1.20040929102021.0284c040@mail.ros.com.au> X-Sender: errol@mail.ros.com.au (Unverified) Date: Wed, 29 Sep 2004 10:25:35 +1000 To: cygwin@cygwin.com From: Errol Smith Subject: Re: "which" command does not expand "~" in path (base-files update needed) In-Reply-To: References: <20040928194018.GR26145@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-IsSubscribed: yes At 05:43 AM 29/09/2004, Brian Ford wrote: > > export PATH=~/bin:$PATH > >How 'bout using a temp, or just plain $HOME as suggested before? Good question, I'd like to know what was wrong with my (first ever cygwin) patch! ;-) Seriously though, is there any advantage to using ~ over $HOME? the bash man page states that ~ maps to $HOME anyway: "If this login name is the null string, the tilde is replaced with the value of the shell parameter HOME. If HOME is unset, the home directory of the user executing the shell is substituted instead. Other-wise, the tilde-prefix is replaced with the home directory associated with the specified login name." Errol -- 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/