zlacker

[parent] [thread] 5 comments
1. freewo+(OP)[view] [source] 2013-06-26 04:45:28
Thats what tab completion is for.
replies(1): >>quacke+A
2. quacke+A[view] [source] 2013-06-26 05:01:38
>>freewo+(OP)
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!

replies(1): >>kanema+h1
◧◩
3. kanema+h1[view] [source] [discussion] 2013-06-26 05:15:18
>>quacke+A
Just prefix the space with a backslash. Eg: ``$ ls /foo/bar/my\ directory/``. With that backslash in place, you can continue your tab-completion.
replies(1): >>iSnow+G2
◧◩◪
4. iSnow+G2[view] [source] [discussion] 2013-06-26 05:55:40
>>kanema+h1
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.

replies(1): >>emillo+67
◧◩◪◨
5. emillo+67[view] [source] [discussion] 2013-06-26 07:46:35
>>iSnow+G2
You can quote the space:

    mkdir x\ y
    cd x' 'y
(or the entire part: cd 'x y')
replies(1): >>quacke+m8
◧◩◪◨⬒
6. quacke+m8[view] [source] [discussion] 2013-06-26 08:17:18
>>emillo+67
Yup, that's what I do too, or %20 if its a url
[go to top]