X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 23 Oct 2008 10:57:55 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: A $ in my path... In-Reply-To: <20132275.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20132275.post@talk.nabble.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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 -- 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/