You are not logged in.
I think it was after I last updated or the time before that.. but for whatever reason, cd is ignoring my attempts to escape the spaces in filenames.
ex:
$ cd Server\ Backup/
bash: cd: Server: No such file or directory
It's a little annoying, and as much as I want to I can't just go renaming all of my friends's directories.
Has anyone else experienced this?
Last edited by SudoGrep (2012-03-31 02:59:48)
Offline
Cannot reproduce:
[karol@black foo5]$ file foo\ bar\ baz/
foo bar baz/: directory
[karol@black foo5]$ cd foo\ bar\ baz/
[karol@black foo bar baz]$ Are you using tab-completion e.g. 'cd Server<tab>' should complete the directory name.
Offline
I know tab completion, and that's exactly what I'm using to generate that.
$ file Server\ Backup/
Server Backup/: directory
Everything else works, it's just cd that's being ridiculous.
Offline
Try it like this:
cd ./Server\ Backup/Although you are much better off not using invalid characters if you can help it.
Offline
It seems no one asked what shell you are using. I am using bash and cannot reproduce your bug. Does installing bash-completion make a difference?
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
Although you are much better off not using invalid characters if you can help it.
The only invalid characters for filenames in UNIX are forward slashes and nulls. [don't quote me on that, my point is that spaces are valid characters and programs should handle them properly]
It seems no one asked what shell you are using.
The output in the OP seems to imply bash ![]()
@SudoGrep: you say you're using tab completion to get that line. Does it work by just manually typing a backslash space there?
Last edited by jac (2012-04-01 12:31:44)
Offline
Does "chdir" work? May be something in your bashrc / zshrc file that's messing you up.
Offline
May be something in your bashrc / zshrc file that's messing you up.
I agree. Have a look at the output of
type cdto see what’s going on.
Offline
The only invalid characters for filenames in UNIX are forward slashes and nulls. [don't quote me on that, my point is that spaces are valid characters and programs should handle them properly]
I will quote you anyway! Some filesystems allow the forward slash. But you're right... I don't know any where space isn't allowed.
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline