Re: dealing with spaces in paths

2007-01-11 Thread Larry Hall (Cygwin)
Morgan Gangwere wrote: On 1/11/07, Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote: Brian Dessent wrote: > "Larry Hall (Cygwin)" wrote: > >> homedir=`cygpath -w "$USERPROFILE"` >> mount -buf "$homedir" "$HOME"/myh >> >> This is recreated from memory because I don't have access to Cygwin now. >>

Re: dealing with spaces in paths

2007-01-11 Thread Morgan Gangwere
On 1/11/07, Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote: Brian Dessent wrote: > "Larry Hall (Cygwin)" wrote: > >> homedir=`cygpath -w "$USERPROFILE"` >> mount -buf "$homedir" "$HOME"/myh >> >> This is recreated from memory because I don't have access to Cygwin now. >> But this is essentially wh

Re: dealing with spaces in paths

2007-01-11 Thread Larry Hall (Cygwin)
Brian Dessent wrote: "Larry Hall (Cygwin)" wrote: homedir=`cygpath -w "$USERPROFILE"` mount -buf "$homedir" "$HOME"/myh This is recreated from memory because I don't have access to Cygwin now. But this is essentially what worked fine for me last night. Note, the quote around USERPROFILE is im

Re: dealing with spaces in paths

2007-01-11 Thread Brian Dessent
"Larry Hall (Cygwin)" wrote: > homedir=`cygpath -w "$USERPROFILE"` > mount -buf "$homedir" "$HOME"/myh > > This is recreated from memory because I don't have access to Cygwin now. > But this is essentially what worked fine for me last night. Note, the > quote around USERPROFILE is important. Ho

Re: dealing with spaces in paths

2007-01-11 Thread Larry Hall (Cygwin)
David Bear wrote: Larry Hall (Cygwin) wrote: David Bear wrote: I'm attempting to script building mount points in order to handle spaces in file names. So I do something like this: homedir=`cygpath -w $USERPROFILE` mount -buf "\"$homedir\" $HOME/myh When I echo the mount command to the syntax

Re: dealing with spaces in paths

2007-01-10 Thread Morgan Gangwere
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Bear wrote: > On Wed, Jan 10, 2007 at 07:26:44PM -0700, Morgan Gangwere wrote: > David Bear wrote: I'm attempting to script building mount points in order to handle spaces in file names. So I do something like this: homedir=`c

Re: dealing with spaces in paths

2007-01-10 Thread David Bear
David Bear wrote: > I'm attempting to script building mount points in order to handle spaces > in file names. So I do something like this: > > homedir=`cygpath -w $USERPROFILE` > mount -buf "\"$homedir\" $HOME/myh > > When I echo the mount command to the syntax looks correct. > > However, whe

re: dealing with spaces in paths

2007-01-10 Thread Morgan Gangwere
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Bear wrote: > > I'm attempting to script building mount points in order to handle spaces in > > file names. So I do something like this: > > > > homedir=`cygpath -w $USERPROFILE` > > mount -buf "\"$homedir\" $HOME/myh > > > > When I echo the mou

Re: dealing with spaces in paths

2007-01-10 Thread David Bear
Larry Hall (Cygwin) wrote: > David Bear wrote: >> I'm attempting to script building mount points in order to handle spaces >> in file names. So I do something like this: >> >> homedir=`cygpath -w $USERPROFILE` >> mount -buf "\"$homedir\" $HOME/myh >> >> When I echo the mount command to the synta

Re: dealing with spaces in paths

2007-01-10 Thread Larry Hall (Cygwin)
David Bear wrote: I'm attempting to script building mount points in order to handle spaces in file names. So I do something like this: homedir=`cygpath -w $USERPROFILE` mount -buf "\"$homedir\" $HOME/myh When I echo the mount command to the syntax looks correct. However, when I actually run th

dealing with spaces in paths

2007-01-10 Thread David Bear
I'm attempting to script building mount points in order to handle spaces in file names. So I do something like this: homedir=`cygpath -w $USERPROFILE` mount -buf "\"$homedir\" $HOME/myh When I echo the mount command to the syntax looks correct. However, when I actually run the mount command via

RE: Spaces in Paths

2005-03-28 Thread Stephan Mueller
PM To: cygwin@cygwin.com Cc: Buchbinder, Barry (NIH/NIAID) Subject: Re: Spaces in Paths Buchbinder, Barry (NIH/NIAID) wrote: > Changing > > program files >to > progra~1 >might also work. > --- It _might_, is true. But if you turn off short-filename g

Re: Spaces in Paths

2005-03-28 Thread zzapper
On Mon, 28 Mar 2005 12:50:12 -0800, wrote: >zzapper wrote: > >>Hi, >>Mysql has now moved under c:/program files/ >>My backup bash script will run correctly if I use the follwing syntax >>/cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params >>However it doesn't work if I

Re: Spaces in Paths

2005-03-28 Thread Linda W
Buchbinder, Barry (NIH/NIAID) wrote: Changing program files to progra~1 might also work. --- It _might_, is true. But if you turn off short-filename generation on NT file systems to speed up NTFS performance and reduce the space needed for directory entries, it won't: REGEDIT4 [HKEY_

Re: Spaces in Paths

2005-03-28 Thread Linda W
zzapper wrote: Hi, Mysql has now moved under c:/program files/ My backup bash script will run correctly if I use the follwing syntax /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params However it doesn't work if I try to load the above into a variable eg mysqldump='/cygdr

RE: Spaces in Paths

2005-03-28 Thread Buchbinder, Barry (NIH/NIAID)
At Monday, March 28, 2005 1:01 PM, zzapper wrote: > On Mon, 28 Mar 2005 12:42:58 -0500, wrote: >> >> Have you tried the following: >> >>mysqldump="/cygdrive/c/program files/mysql/MySQL Server >> 4.1/bin/mysqldump.exe""$mysqldump" $params >> >> Without the double-quotes around the actua

Re: Spaces in Paths

2005-03-28 Thread zzapper
On Mon, 28 Mar 2005 12:42:58 -0500, wrote: > >Have you tried the following: > >mysqldump="/cygdrive/c/program files/mysql/MySQL Server > 4.1/bin/mysqldump.exe" >"$mysqldump" $params > >Without the double-quotes around the actual call, the variable gets >split at spaces such that only th

Re: Spaces in Paths

2005-03-28 Thread Jean-Sebastien Trottier
On Mon, Mar 28, 2005 at 05:15:07PM +0100, zzapper wrote: > Hi, > > Mysql has now moved under c:/program files/ > > My backup bash script will run correctly if I use the follwing syntax > > /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params > > However it doesn't work

Re: Spaces in Paths

2005-03-28 Thread Andrew Schulman
> >> mysqldump='/cygdrive/c/program\ files/mysql/MySQL\ Server\ > >> 4.1/bin/mysqldump.exe' > >> > >> I get "/cygdrive/c/program\: No such file or directory..." > >> > >> Is this just hard luck? > > > >Nope, just the way the quoting rules work. You've already quoted the spaces > >by > >using th

Re: Spaces in Paths

2005-03-28 Thread zzapper
On Mon, 28 Mar 2005 11:34:12 -0500, wrote: >zzapper wrote: >> Hi, >> >> Mysql has now moved under c:/program files/ >> >> My backup bash script will run correctly if I use the follwing syntax >> >> /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params >> >> However it

Re: Spaces in Paths

2005-03-28 Thread Andrew DeFaria
Jonathan Arnold wrote: zzapper wrote: Hi, Mysql has now moved under c:/program files/ My backup bash script will run correctly if I use the follwing syntax /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params However it doesn't work if I try to load the above into a vari

Re: Spaces in Paths

2005-03-28 Thread Jonathan Arnold
zzapper wrote: Hi, Mysql has now moved under c:/program files/ My backup bash script will run correctly if I use the follwing syntax /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params However it doesn't work if I try to load the above into a variable eg mysqldump='/cygd

Spaces in Paths

2005-03-28 Thread zzapper
Hi, Mysql has now moved under c:/program files/ My backup bash script will run correctly if I use the follwing syntax /cygdrive/c/program\ files/mysql/MySQL\ Server\ 4.1/bin/mysqldump.exe $params However it doesn't work if I try to load the above into a variable eg mysqldump='/cygdrive/c/prog

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-28 Thread Christopher Faylor
On Fri, Feb 28, 2003 at 10:14:48PM -0500, Pierre A. Humblet wrote: >The problem is being addressed and will be solved perfectly (time will tell !) >soon. Hmm. TPIBA. I like it. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-28 Thread Pierre A. Humblet
On Fri, Feb 28, 2003 at 04:42:53PM -0800, Curtis Siemens wrote: > > By the way, given that I can actually run an executable that bash/type > can't find, does this suggest that possibly the builtin type command > is doing something wrong? Yes and no. Obviously it isn't working as it should. But in

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-28 Thread Curtis Siemens
Thanks for the responses. I managed to narrow down what's different in my situation. Basically the bash builtin type command does work fine with paths that contain spaces. The problem is a "side effect" of using NTFS and accidentally banging my head into NT's horrible over complicated/complex Sec

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-28 Thread Gareth Pearce
- Original Message - From: "Ronald Landheer-Cieslak" <[EMAIL PROTECTED]> To: "Curtis Siemens" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, February 28, 2003 9:05 PM Subject: Re: bash's (built-in) type command can not handle spac

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-28 Thread Ronald Landheer-Cieslak
On Thu, 27 Feb 2003, Curtis Siemens wrote: > How To Reproduce: > - > Install Cygwin under c:\ or c:\cygwin - some directory that doesn't NEVER DO THAT! see http://cygwin.com/faq/faq_2.html#SEC9 rlc -- Unsubscribe inf

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-27 Thread Jeremy Hetzler
At 01:51 AM 2/28/2003 -0800, Jeremy Hetzler wrote: What is different about your particular installation, I have no idea. Actually, one idea. Your 'type' might be an alias or function that fails to quote its arguments properly. Try "builtin type -a type". If it doesn't return precisely "type is

Re: bash's (built-in) type command can not handle spaces in paths

2003-02-27 Thread Jeremy Hetzler
At 03:19 PM 2/27/2003 -0800, Curtis Siemens wrote: Cygwin's type command (built into bash.exe) does not work for executables that are under a directory that has spaces. Well, it seems to work OK for me: --- 501 $ mkdir /foo\ bar 502 $ touch /foo\ bar/baz 503 $ chmod a+x /foo\ bar/baz 504 $ PATH=/us

bash's (built-in) type command can not handle spaces in paths

2003-02-27 Thread Curtis Siemens
My platform is Windows 2000 (with all the latest patches). This problem probably occurs on a number of Windows platforms. I'm using the latest released Cygwin with Cygwin DLL release version 1.3.20-1 I've searched the Web/Faq/Documentation/Mailing-Lists and haven't seen any reference to this prob