vim-plug VS nvim-lspconfig

Some examples are vim-plug, vundle, or, lazy.nvim.

👉 If you are missing a plugin, you can easily install or uninstall it using vim.plug. For more information, please visit vim.plug on GitHub or I'd be happy to advise you see about us.

I have been talking about plugins since the beginning of the article, but using a simple editor doesn't involve doing everything by hand. So I have been using a plugin manager for a long time and if you don't, I strongly advise you to get started: it's very practical. I used Vim plug which was everything I like: simple and effective.

vim-plug

Did you really install VimTeX? Did you run :PlugInstall? Ensure you installed and set up vim-plug correctly (https://github.com/junegunn/vim-plug). If VimTeX is installed, it should be installed to '~/.vim/plugged', thus you can open a terminal, then cd ~/.vim/plugged/vimtex and you should find the files there.

If you're determined to use vim for some reason, I'd suggest checking out vim-plug: https://github.com/junegunn/vim-plug. Quite useful for installing and maintaining all of the plugins that you're going to need to get vim to provide even a subset of the features offered by modern editors.

I encourage you to add plugins to your vim (tip: use vim-plug). Use vimawesome.com for inspiration.

Personally, I like https://github.com/junegunn/vim-plug

But the plugin manager https://github.com/junegunn/vim-plug can also install from offline sources, without accessing Github:

Packages that we will use : blink.cmp for autocompletion, typescript-tools for the typescript LSP, neovim/nvim-lspconfig to set up the LSP, and Mason so we can install volar.

Check configs.md to ensure your language's LSP server is present there and edit the configs/lspconfig.lua file to add your language's LSP.

Neovim Install the nvim-lspconfig plugin to make configuration of the LSP client simpler. Then update your init.lua to tell Neovim which filetypes to use the language server for (i.e. .kt and .kts extensions). The LSP client will try to the start the sever by running the kotlin_language_server binary. You can directly point Neovim to the location of the binary, or include this directory in your $PATH.

👉 With LSP in this installation, I use Coc for its simplicity without the need to intervene in the Coc configuration. LSP has been very useful in my Helix modal editor to configure Helixu.

neovim/nvim-lspconfig: Quickstart configs for Nvim LSP

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

Adding language support it neovim isn't very difficult once you're setup. I use nvim-lspconfig[1] and just about any language you could need is documented[2]. But like others have mentioned there are batteries included distributions of neovim if that's your cup of tea.

[1]: https://github.com/neovim/nvim-lspconfig/

[2]: https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

If we can't find the basic usage in the documentation we can go to nvim-lspconfig's github repository. In there we look for a folder called server_configurations, this contains configuration files for a bunch of language servers.

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.