Skip to main content

Timeline for cd .. on root folder

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Apr 25, 2014 at 9:09 comment added celtschk If root didn't have .., you could just do while [ -d .. ]; do cd ..; done
Apr 24, 2014 at 20:07 comment added kagali-san btw, I think that ../.. with relative_to_/_depth+1 - must redirect back to current directory (imagine broke symlinks fun after that one)
Apr 24, 2014 at 20:05 comment added kagali-san @musiphil typing spaces in between commands - is a logic error (assumption that all spaces between tail -f | grep are a must). Most unix folks suffer from it. Typing '../..' looks like a Windows-folk problem (by default, cmd starts in X:\Windows and you have to spam .. from the beginning). Why to heal a small problem when there's a larger one? (spaces)
Apr 24, 2014 at 4:40 comment added musiphil Repeating ../ more times than needed and wishing it to work as intended looks like a (dormant) logic error to me, even if the filesystem apparently allows it.
Apr 24, 2014 at 0:58 comment added jamesdlin The flip side is that maybe you accidentally enter too many ../s and operate on (or remove) a file you didn't intend to without error.
Apr 23, 2014 at 7:18 comment added Skylar Ittner @Bach Sometimes, keyboard mashing is more fun. Besides, in many circumstances you're not trying to go to the root, in which case using ../ is better. I also do a lot of file operations in PHP, where I can't do / for several reasons.
Apr 23, 2014 at 7:02 comment added Bach What's wrong with cd /?
Apr 23, 2014 at 5:25 history answered Skylar Ittner CC BY-SA 3.0