zlacker

Unless your ssh'd into a machine, it's annoying to type long dir's. What's worse is compensating for spaces in filenames.

>>quacke+(OP)
Thats what tab completion is for.

>>freewo+b
Thank you freework, didn't know about that one (embarrassing as it is to admit).

Still sucks dealing with spaces when it comes to command processes like ffmpeg -i <no_tab>...but awesome for cd'ing or ls'ing!

>>quacke+L
Just prefix the space with a backslash. Eg: ``$ ls /foo/bar/my\ directory/``. With that backslash in place, you can continue your tab-completion.

>>kanema+s1
Still, on some international keyboards, backspace is hard to reach, eg. on a German Mac keyboard, is it <alt><shift>7.

So don't put spaces in path names, it's a bitch to work with.

>>iSnow+R2
You can quote the space:

    mkdir x\ y
    cd x' 'y

(or the entire part: cd 'x y')

>>emillo+h7
Yup, that's what I do too, or %20 if its a url

>>quacke+(OP)
Unix/Linux/whatever should have just forbidden spaces in filenames in the first place since none of the basic tools make it easy iterate over a list of filenames with spaces correctly.

>>J_Darn+jo
At least UNIX doesn't have a space in the path of the main programs directory (I'm looking at you Windows).

Also, many of the basic tools have a -0 option which uses the null character to replace many uses of space. Still far from an adequate solution though.

>>gizmo6+RG
Ohh yeah! This is where my initial frustrations have always been for spaces...mounting an NTFS-3G or URL encodings.