4 ms·
We 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 b
by strainer 8y ago
We 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.)