X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<20135109.post@talk.nabble.com>
Date:	Thu, 23 Oct 2008 09:50:43 -0700 (PDT)
From:	ProblematicRoutes <cgf AT syntilect DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: A $ in my path...
In-Reply-To:	<f60fe000810230757u5d00a7breeb088f90868fb45@mail.gmail.com>
MIME-Version:	1.0
X-Nabble-From:	cgf AT syntilect DOT com
References:	<20132275 DOT post AT talk DOT nabble DOT com> <f60fe000810230757u5d00a7breeb088f90868fb45 AT mail DOT gmail 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

Mark J. Reed wrote:
> 
> 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.
> 

Dear Mark, Sid

I'm not sure why it is being expanded then, but if I use includes in latex
(for example, \input{../someinclude.tex}) or a script like the following
that causes the problem to occur with cygwin:

#!/bin/bash

echo Committing /cygwin directory in repo:
svn ci ~

I will try yours and Sid's solutions tomorrow (I think they're the same
idea? Correct me if I've misunderstood your suggestion!)  when I'm back in
the office, and hopefully they will fix the problem.

Andrew
-- 
View this message in context: http://www.nabble.com/A-%24-in-my-path...-tp20132275p20135109.html
Sent from the Cygwin list mailing list archive at Nabble.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 -