X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<f60fe000810230757u5d00a7breeb088f90868fb45@mail.gmail.com>
Date:	Thu, 23 Oct 2008 10:57:55 -0400
From:	"Mark J. Reed" <markjreed AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: A $ in my path...
In-Reply-To:	<20132275.post@talk.nabble.com>
MIME-Version:	1.0
References:	<20132275 DOT post AT talk DOT nabble DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Thu, Oct 23, 2008 at 10:34 AM, ProblematicRoutes wrote:
> $ pwd
> //sbs01/students_home$/csmith
>

> This $ sign causes problems everywhere - with latex, with svn, with anything
> that uses ~ to refer to my home directory, because it expands to ...$/...
> and bash tries to parse the $/ as a variable.

Really?  I'm hard-pressed to think of ways that you could use ~ or
$HOME that would then lead to the result of that expansion being
re-analyzed for further parameter expansion as well.  It seems like
you'd have to go out of your way to make that be a problem.

But the workaround, if you have the privileges to do it, would be to
make a $-less symbolic link and change your passwd entry to match.

-- 
Mark J. Reed <markjreed AT gmail DOT com>

--
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/

- Raw text -