How to Do 90% of What Plugins Do (With Just Vim)

What people said

farisjarrah · 2021-11 · Strong recommendation

The thoughtbot series on vim is great. I'm really glad I found this video early in my Vim career. I've got a very minimal vimrc as a result and just try to lean into the vim builtins [VIDEO]

Read the original HN comment ↗

skydhash · 2025-04 · Recommendation

With editors like vim, neovim, emacs, it's way easier to get the lay of the land first (tutorial, play around with the default config,..) and then list out what you need. My vim config has three things only: LSP, FZF (for anything fuzzy), and Plug (to install the above two). There's also a few niceties, but I could do without them. or vendor them into the main config. But it's not my daily editor, so that's just the base config. Anything I could add on top of that would depend on the projects I would need it for. That's about 200 lines (the lsp config is 1/4 of that) NB. A nice talk even if it's about vim "How to Do 90% of What Plugins Do (With Just Vim)" [VIDEO]

Read the original HN comment ↗

gregjor · 2025-02 · Recommendation

> The ability to autocomplete, and navigate through the code (even my dependencies's code) by the click on a function, the popover showing the documentation/signature of the function i'm going to call. Those are Quality of Life features I'm not ready to give up on. ctags did most of that decades ago. Plain vim has good autocomplete and signature popovers, along with navigating to functions and class definitions. No LSP needed. An LSP will do it better but with sometimes significant overhead. As I noted I don't use VSCode or a JetBrains IDE. I know about them and have used them. My setup works language-agnostic, and I also work in multiple languages. Possibly useful, at least interesting: [VIDEO]

Read the original HN comment ↗