7 ms·
> Don't put any lines in your vimrc that you don't understand. Actually true for most human-configurable setting files.
by lifthrasiir 10y ago
> Don't put any lines in your vimrc that you don't understand.
Actually true for most human-configurable setting files.
- divbit 10y agoI sort of disagree with this and think one should extend in the opposite direction- to keep sharp, have an RNN generate some plausible config options / shell commands, and append them to the bottom of your vimrc / bashrc on startup. This results in sort of like a 'chaos monkey' of coding, to prepare you for when real emergencies pop up.
- afarrell 10y agoHuh? The point of a Chaos Monkey is to simulate failures that might happen in real life. How does this do so?
- divbit 10y agoDon't tell me you've never accidentally rm -rf'd something important
- iamdave 10y agoDon't tell me your default method for deleting files is to carelessly throw 'rm -rf' at the issue...if it's "important" and you're using -rf, a part of me thinks "you deserve whatever happens"
- divbit 10y agoI was joking in both comments (clearly running arbitrary shell commands on a personal computer is a terrible idea), but it's not like a careless rm -rf has never happened before
- deleted 10y ago[deleted]
- mhink 10y agoOooh, I really like this idea.
- gkya 10y agoWell when I did a vimrc there was no single line in my vimrc that I really understood. VimL reads like output from a keylogger.
- dotancohen 10y agoActually, VIM remaps _are_ little more than the output from a keylogger! A keylogger recording a VIM session, no less.
- yjftsjthsd-h 10y agoWell... Yes. It's the same command language that's used to drive vim by hand, so it should resemble a keylog of doing those actions.