/mnt/Windows/Progam\ Files
What do I enter in the bash profile so that the shell will handle directory names with spaces? KDE has no problems going into say /mnt/Windows/Progam Files but bash chokes on dir names that contain spaces.. SuSE 9, Drake 9.1 I forget which I was using at the time....
/mnt/Windows/Progam\ Files
I know that \ will work on a case by case basis, but I am looking for something a little more seemless -some of the default Linux installs of various distros the bash shell has no trouble with spaces, but not others -I guess I should just figure out which and examine the bash profile differences. I just thought someone might know the tweak off the top of thier head.
I get frustrated when I do a command like
cp -ax /some/directory /to/destination
and it chokes on a subdirectory somewhere that contains a space in the name
cp -ax /some/directory /to/destination should /not/ choke if it hits a space, the only times spaces effect anything is when inputting them, and you just need a \ or put the whole thing in quotes (eg "/foo/Program Files"![]()
hello,
i just use cp -R and never have an issue
e.g.
Code:[pbharris@bugs ~/tmp]ls -R crappo/ crappo/: space one space three space two crappo/space one: crap poo hoo crappo/space one/crap: crappo/space one/poo hoo: poo three crappo/space one/poo hoo/poo three: crappo/space three: crappo/space two: [pbharris@bugs ~/tmp]cp -R crappo morecrappo [pbharris@bugs ~/tmp]ls -R morecrappo/ morecrappo/: space one space three space two morecrappo/space one: crap poo hoo morecrappo/space one/crap: morecrappo/space one/poo hoo: poo three morecrappo/space one/poo hoo/poo three: morecrappo/space three: morecrappo/space two:
gorn -you're right, bad example on my part
just trying to figure out why I have problems with some default bash configurations and not others
pbharris -sometimes you are too funny, are you sure you were not the "old fart" in the now defunct "linux lounge" forums?
Bookmarks