Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They could have saved some time by trying to reproduce the bug while running `vim -u NONE`.

The first thing I do when I encounter a problem in vim is to run it a) without plugins, b) without my .vimrc, and c) with neither plugins nor rc.



exactly; in the emacs community, when somebody is chasing down a weird bug, they get asked to run emacs with the flags that disable all the startup customization as the very first thing, because 90% of the time, its a problem with some interaction in the user's (byzantine) ~/.emacs.d


Awesome, this will be helpful in tracking down some weird behavior I'm currently seeing in vim...


I didn't know that was a thing! Sweet, thanks - this'll totally be useful in the future!




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: