julia-vim VS nvim-lspconfig

There's a handy Vim plug-in for Julia that will convert latex commands to symbols so it's a one character difference for a pretty notable improvement to readability when you start to get into longer equations.

Nowadays during my master thesis does lots of equations appear in my python code, but I would love to use tex rendering in some way, like latex preview in emacs. However, I know that there is some great latex rendering such as tex-conceal.vim and latex_to_unicode in julia-vim, but I am not able to make it work for python comments. Any idea on how to solve this?

There is a plugin I tried which is called julia-vim. However, this plugin is too broken for me. It conflicts with other completion plugins which makes it so hard to either fix or manage my configuration and keymaps. Fortunately, I found cmp-latex-symbols, a completion plugin that as described in the README

I use Git and plain text files. The Julia addon for Vim allows one to write UTF-8 math symbols with LaTeX commands.

I use julia.vim for unicode support. I find it a bit more responsive than agda-vim, and it has more symbols (the list is autogenerated). but I have two gripes with it:

Ideally, yes, I want to use LSP in order for it to work as close as possible from my nvim with julia-vim, coc.nvim and vim-julia-cell. At least until I'm more familiarized with Emacs. I really do want to learn, but I cannot just stop my daily work, so the best world possible would be to be able to keep working while learning.

I use vim+vim_slime along with the julia plugin configured with tab latex to unicode conversion. This means I can have a REPL open in a split vim buffer and send chunks from my script directly to the REPL. It's really lightweight and fast. I'm working to make some functional snippets too.

Since I was still missing some more advanced Vim features, I did some search and now have a pretty decent terminal based environment. The base is Tmux + Neovim- I open 2 panes, where one is used for coding and the other is Julia REPL. I use julia-vim plugin for base syntax and code highlights and vim-slime with vim-julia-cell for live sending of the code from the Neovim to the REPL.

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.

This specific issue talks about fixing clangd for that error: https://github.com/neovim/nvim-lspconfig/issues/2184. The issue is ongoing for ccls AFAIK but for clangd, this has been discussed and fixed in the past already.

I am trying to set up the pbkit language server for protobuf files. Since it is not part of the nvim-lspconfig repo's server configurations, I have to figure the way out myself. It doesn't seem to be too difficult, as I can start from the bufls configuration there. The following is what I have at the moment:

I have configured neovim with lspconfig and mason. Added the suggested configuration of the lsp config(https://github.com/neovim/nvim-lspconfig) to ~/.config/nvim/after/plugin/lsp.lua Then I installed via mason the following language servers:

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Basically neovim can act as a client to a variety of different language servers (https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...) which give neovim IDE capabilities. This can be done in original Vim also but requires external plugins which can be a pain to compile and install. Neovim has it built in.

I'm struggling to get [sqlls](https://github.com/joe-re/sql-language-server) with [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig) to use Postgres syntax.