5 ms·
The vi editor causes brain damage [2007]
- lutusp 13y agoThere are good arguments against vi, its variations and descendants. This isn't one of them.
- hk__2 13y agoNot anymore: $ mkdir bar $ cd bar $ for i in {1..40000};do touch $i;done # create 40k files $ rm * $ # no warning But it has nothing to do with `rm` itself, it was due to the fact that the glob expansion was done by Bash.
- sharth 13y agoApparently a kernel fix was the cure: http://article.gmane.org/gmane.linux.kernel/571954 http://article.gmane.org/gmane.linux.kernel/571954 and the patches are at: https://lkml.org/lkml/2007/6/13/67 https://lkml.org/lkml/2007/6/13/67
- pyalot2 13y agoThis behavior is encountered whenever * is expanded by the shell and has nothing to do specifically with vi or rm. I also fail to see how posting a troll comment from a mailing list from a person who fundamentally doesn't understand the *nix CLI environment belongs here.
- niuzeta 13y agoI clicked the link with excitement that this was some sort of intellectual discourse on implication on brain of stationary posture while computing(i.e., not moving hands away from keyboard for a very long time). I am disappointed.
- H3g3m0n 13y agoWouldn't rm as part of GNU binutils, be more likely written in Emacs?
- thesmok 13y agoJust find . -type f -exec rm -f {} \; I had to do this when I had to delete millions of cache files and rm couldn't do that.
- gmagogsfm 13y agoi tried to google this dude and found what could be his website, but when I click on it, my company network blocks me and says it has nudity