vim-lsp-ale VS neovim

ALE can use LSP as well. And if you are using vim-lsp, you can use the same instance of server for both with vim-lsp-ale bridge plugin.

Don't you need vim-lsp-ale for that? It puts lint results from vim-lsp into ALE's interface so ALE doesn't need to run a second lsp server. Which seems to be another way of saying ALE uses it as a source.

However; apparently this causes two LSP's to run. Instead of nvim's default lsp; there is also prabirshrestha/vim-lsp and mattn/vim-lsp-settings that runs LSP's. There is rhysd/vim-lsp-ale to fix the concurrent LSP running between Ale and vim-lsp, and shun/ddc-vim-lsp which integrates vim-lsp with ddc.vim

See comment here for a setup with vim-lsp. Add ale for lint support and vim-lsp-ale to put lsp linting into ale.

ALE is primarily for linting (although it may also serve as basic LSP client). The protocol itself is for code completion, hover tips, navigation, workspace symbols, finding references, highlighting, renaming, reformatting, refactoring etc. And also diagnostics (which you can integrate with ALE via vim-lsp-ale).

I looked at this earlier and was unsure if this is in lieu of ALE or in addition to ALE. I saw a post about also needed - How can I use ALE and vim-lsp together? When I looked into vim-lsp-ale I was unsure about how to configure PLS for perl.

Try vim-lsp-ale to get vim-lsp lint errors to show in ale. You should turn off all other linters unless you actually need them.

Sorry I should have mentioned I'm using ALE for linting/fixing. Would I have to remove ALE to use Neovim's native LSP, or use a plug-in like this I'm assuming?

To me "integrated" means I do everything from one application -- no building in the shell etc. I think the biggest knock against "integrated" is when vim plugins don't work together (like ale and lsp before vim-lsp-ale).

Hello! I thought I'd mention this plugin to people, as people might not know about it. rhysd on GitHub has put together a plugin that connects vim-lsp to ALE, completely without much, if any, help from me. I think it's pretty cool, and it could be useful for someone. Check it out.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.