the constant tweeking time sink to vim is a symptom not the norm. with releases like neovim and onivim one has those same tweeks baked in.
Honestly thought, if one is only using vim for home row navigation then they're missing the point. try to disable cusor movement by unbinding the keymaps and start to use vim mode as it's intended, a command prompt.
did anyone know that :r!foo.sh will actually read into the current buffer the strout of "foo.sh" or :split !fu.sh will bring a new horizontal rule window with the output of that shell command?
how about :set makeprg=... ? or the scripting language that's built-in?
I'm proud to say that vim has made me a better developer because it's been a tool which always is there, is built by programmers for programmers and just works for any use.
And that's the point of it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
the constant tweeking time sink to vim is a symptom not the norm. with releases like neovim and onivim one has those same tweeks baked in.
Honestly thought, if one is only using vim for home row navigation then they're missing the point. try to disable cusor movement by unbinding the keymaps and start to use vim mode as it's intended, a command prompt.
did anyone know that :r!foo.sh will actually read into the current buffer the strout of "foo.sh" or :split !fu.sh will bring a new horizontal rule window with the output of that shell command?
how about :set makeprg=... ? or the scripting language that's built-in?
I'm proud to say that vim has made me a better developer because it's been a tool which always is there, is built by programmers for programmers and just works for any use.
And that's the point of it.