4 ms·
Hopefully they have read the Jargon File: http://www.catb.org/jargon/html/D/DWIM.html http://www.catb.org/jargon/html/D/DWIM.html > Warren Teitelman originall
by tniemi 8y ago
Hopefully they have read the Jargon File:
http://www.catb.org/jargon/html/D/DWIM.html http://www.catb.org/jargon/html/D/DWIM.html
> Warren Teitelman originally wrote DWIM to fix his typos and spelling errors, so it was somewhat idiosyncratic to his style, and would often make hash of anyone else's typos if they were stylistically different. Some victims of DWIM thus claimed that the acronym stood for 'Damn Warren’s Infernal Machine!'.
> In one notorious incident, Warren added a DWIM feature to the command interpreter used at Xerox PARC. One day another hacker there typed delete * $ to free up some disk space. (The editor there named backup files by appending $ to the original file name, so he was trying to delete any backup files left over from old editing sessions.) It happened that there weren't any editor backup files, so DWIM helpfully reported * $ not found, assuming you meant 'delete * '. It then started to delete all the files on the disk! The hacker managed to stop it with a Vulcan nerve pinch after only a half dozen or so files were lost.
> The disgruntled victim later said he had been sorely tempted to go to Warren's office, tie Warren down in his chair in front of his workstation, and then type delete * $ twice.
- strainer 8y agoWe don't need to be quite as paranoid about the plainness of a directory navigation tool, as needed for a command interpreters path selector. It would need to be combined with potentially destructive operations in a script to be dangerous, so then on thy own head be it.
- jerf 8y agoSuch things have happened: https://www.slashgear.com/steam-on-linux-bug-can-delete-all-users-files-16364945/ https://www.slashgear.com/steam-on-linux-bug-can-delete-all-... The problem is that shell is so sloppy it's hard to know what will happen. Of course, that's not unique to a new mechanism for navigating directories. It's scary stuff no matter what.
- unhammer 8y agoThat was an unbound variable, not due to a tool for predicting what directories you typically navigate to. Who in their right mind would use that in a shell script? (Actually, nevermind, if github had decent code search I'll bet you could find rm -rf --no-preserve-root `fasd somefile` somewhere in there.)