Skip to main content
14 events
when toggle format what by license comment
Nov 19, 2016 at 1:34 answer added Martin Tournoij timeline score: 1
Nov 18, 2016 at 22:16 answer added Petr Skocik timeline score: 4
Nov 18, 2016 at 22:09 answer added Joshua timeline score: 2
Nov 18, 2016 at 21:57 history tweeted twitter.com/StackUnix/status/799733252210692096
Nov 18, 2016 at 16:36 vote accept mbroshi
Nov 18, 2016 at 16:24 comment added Alexej Magura @Rmano this is true: it's just something I wouldn't do on principle: just go up a directory and then delete the current directory. I'm not entirely sure why it's such a big deal--though I have had some misfortunes with the current directory no longer existing, such as relative paths no longer working, but you can always get out by using an absolute path--but some part of me just says that it isn't a good idea in general.
Nov 18, 2016 at 16:22 comment added Rmano @AlexejMagura although I sympathize, I do not see why removing the current directory should be any different than removing an open file. The object will stay alive until a reference to it exists, and then garbage collected afterward. You can do cd ..; rm -r dir with another shell with quite clear semantics...
Nov 18, 2016 at 16:00 answer added 林果皞 timeline score: 31
Nov 18, 2016 at 15:35 comment added mbroshi Agreed--I like the default behavior, but it is not consistent with, e.g., find . -print.
Nov 18, 2016 at 15:23 answer added Thomas timeline score: 16
Nov 18, 2016 at 14:27 comment added Alexej Magura Most likely because removing the current working directory would not be a good idea.
Nov 18, 2016 at 14:24 history edited Jeff Schaller
edited tags
Nov 18, 2016 at 14:16 review First posts
Nov 18, 2016 at 14:24
Nov 18, 2016 at 14:11 history asked mbroshi CC BY-SA 3.0