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: bash, filename completion and spaces in path components [was RE: SSH Environment] Date: Thu, 30 Sep 2004 00:02:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 29 Sep 2004 23:02:34.0361 (UTC) FILETIME=[67F4F690:01C4A678] > -----Original Message----- > From: cygwin-owner On Behalf Of Andrew DeFaria > Sent: 29 September 2004 16:16 > However, one trick that I do to more easily deal with the "Program > Files" think is: > > $ mount -bsf "/cydrive/c/Program Files" /apps > > Then it's simply /apps//. Much easier to deal with, > shorter and file name completion under bash works well with this. I use the same trick myself because a lot of apps can't handle a filename with a space in it, not even if it gets correctly escaped and passed through to argv, but I've never known bash filename completion to have a problem: it escapes all the spaces and other metachars beautifully. Sometimes I use it just to save me having to figure out what needs escaping and what doesn't. What problem do you see? 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/