undefined | Better HN

0 pointsscruple6y ago0 comments

Most of the things you're describing as editor issues would be caught by formatters and linters and a test suite, so I have a hard time understanding where you're coming from with this.

edit/ A word.

0 comments

org34326y ago

This is a good point actually, the sooner you catch the mistake the quicker you can correct it. So once it gets down the line, even in a pre-commit, you're just wasting your own time on getting the feedback. It's not always possible to get it sooner of course.

scrupleOP6y ago

Yep. I have formatters and linters run on save in vim (of course, any editor or IDE can handle this) and the linters render their results in vim, as well. I also use vim-dispatch [0] to handle running builds and test suites asynchronously, but I don't run any auto commands for that, instead preferring to kick those tasks off with a keystroke.

My workflow is crafted in a way to give me, what I have found to be, the tightest feedback loop that I can possibly get with the languages and frameworks and tooling that I use at work. I find that vim, out of every other editor or IDE that I've ever used, is set apart in it's ability to deliver on that requirement.

[0]: https://github.com/tpope/vim-dispatch

j / k navigate · click thread line to collapse

0 comments

org34326y ago

scrupleOP6y ago

[0]: https://github.com/tpope/vim-dispatch

j / k navigate · click thread line to collapse