Vim: avoid plugins. Don't turn it into an IDE. Unix is your IDE and Vim is your editor.
Of my plugins, the only ones which don't add more language support are:
Fugitive, exclusively for :Gblame
hilinktrace, which helps with designing/modifying color schemes
@sir This is why neovim is a thing I believe
@brandon eh not really, I feel like a lot of what NeoVim does is in service of the Vim-as-an-IDE goal
@sir That's what I mean :P
@sir do you use it like Acme but with a keyboard?
@sir so, it can't do the same actions or do you just not use them? thinking of stuff like Edit |pipe, or plumbing (in the Plan 9 ports version), or sending things to a terminal window.
i only know the basic editing actions in Vim plus i played around with YCM a long time ago, so i really have no idea how well these work in it. but these are what i think of when i think of a "the OS is your IDE" workflow.
@grainloom when I say "the OS is my IDE", I don't mean integrations between vim and my OS. I mean getting out of vim and using my shell.
@sir My list:
- Fugitive, exclusively for :Gdiff, which in turn is exclusively for "revert this hunk".
I can't help feeling Fugitive is a violation of our rule.
I used to rely on signify as well, but it has now been 'depackaged': https://mastodon.social/@akkartik/103994830568601931. One day I'll do the same for Fugitive.
> Vim: avoid plugins. Don't turn it into an IDE. Unix is your IDE and Vim is your editor.
> Of my plugins, the only ones which don't add more language support are:
> Fugitive, exclusively for :Gblame
> hilinktrace, which helps with designing/modifying color schemes
Strong agree, though I'd sub in fzf for Ctrl-P. Oh, and add vim commentary, but I almost feel like it and vim-surround don't count – Tim Pope has a gift for writing native-seeming plugins
@sir what's editorconfig?
@reto you can have all of those things in your shell, and bonus: rig them up to your CI or write scripts for them
@reto This is an old debate that doesn't bear rehashing. Certainly there's room for both sides. Vim and IDEs are both good. But *trying to turn Vim into an IDE* is not as good as either. You lose the snappy responsiveness of Vim and the seamless UX of IDEs. And too many plugins destabilize Vim.
Also, one correction: nobody uses grep to jump to definitions. We Unix hands use crags, which Vim integrates with out of the box.
@sir Does vim support variable width fonts yet?
@sir I dunno being able to see linter errors when saving and opening files as well as being able to jump to relevant unit tests are good features imo
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!