HumanLaTeX: a knowledge base for using Neovim+LaTeX in the humanities and social sciences

1. humanlatex

   1 1 - -

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. lsp-zero.nvim

   2 132 3,937 8.6 Lua

   A starting point to setup some lsp related features in neovim.

   

   As for your specific situation, it might be that you're talking about lsp-zero or, more specifically, Mason. Mason is basically a package manager for language servers and it uses npm under the hood. However, if you don't want that kind of bloat on your system, you can do perfectly fine without Mason. In that case, you only install nvim-lspconfig as I describe here, and instead of using Mason to install language servers, you install them manually (system-wide, probably) and point your lspconfig to them. For me, Mason is a nice enough convenience to justify the baggage, but you can easily live without it.

4. mason.nvim

   3 112 8,330 7.2 Lua

   Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.

   

   As for your specific situation, it might be that you're talking about lsp-zero or, more specifically, Mason. Mason is basically a package manager for language servers and it uses npm under the hood. However, if you don't want that kind of bloat on your system, you can do perfectly fine without Mason. In that case, you only install nvim-lspconfig as I describe here, and instead of using Mason to install language servers, you install them manually (system-wide, probably) and point your lspconfig to them. For me, Mason is a nice enough convenience to justify the baggage, but you can easily live without it.

5. nvim-lspconfig

   4 529 11,190 9.8 Lua

   Quickstart configs for Nvim LSP

   

   As for your specific situation, it might be that you're talking about lsp-zero or, more specifically, Mason. Mason is basically a package manager for language servers and it uses npm under the hood. However, if you don't want that kind of bloat on your system, you can do perfectly fine without Mason. In that case, you only install nvim-lspconfig as I describe here, and instead of using Mason to install language servers, you install them manually (system-wide, probably) and point your lspconfig to them. For me, Mason is a nice enough convenience to justify the baggage, but you can easily live without it.

Suggest a related project