ansible-language-server
nvim-lspconfig
Our great sponsors
ansible-language-server | nvim-lspconfig | |
---|---|---|
13 | 523 | |
250 | 9,516 | |
- | 4.3% | |
8.0 | 9.7 | |
about 1 month ago | 2 days ago | |
TypeScript | Lua | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ansible-language-server
-
The Bullhorn #108 (Ansible Newsletter)
Version 1.1.0 The Ansible Language Server (ALS) underwent a substantial upgrade. ALS v1.1.0 has adopted the new YAML 2.x package and successfully updated its code base accordingly. This significant development brings enhanced capabilities in terms of YAML diagnostics and strengthened security measures. Another crucial feature addition was the completion for variables declared inside a playbook. Full list of change-logs here.
-
The Bullhorn #93 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
[Ansible] Visual Studio Code et l’extension Redhat Ansible (quelqu’un peut-il le faire fonctionner) ?
Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :
-
Anyone here have success with Ansible syntax highlightning lsp?
You are conflating multiple functions. I have used the ansible language server 1 with decent success in both 0.7 and 0.8. It provides autocompletion of modules and diagnostics from ansible-lint, but does nothing to address syntax highlighting. Your project should have either an ansible.cfg or .ansible-lint at your project’s top level and your yaml files should be of filetype yaml.ansible. If you run :LspInfo it should display ansiblels as active.
-
LSP configuration
I'm looking to use a language (Ansible flavored YAML) that does have an LSP implementation, but is not supported by tree-sitter.
- How to properly set up LSP ansible language server in emacs, for proper ansible playbook editing support?
-
A new version of vscode ansible extension is out
Does the standalone usage help?
-
The Bullhorn #45 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
Red Hat Ansibe Extension for VSCode
Additionally, I found that the entire extension stopped working because in the past, easy-install had added a .egg file to my python path. I submitted a fix and it was accepted, but I'm not sure if the fixed language server is part of the current extension version. Might be worth checking for files like that in the paths listed in sys.path.
-
Visual Studio Code and the Redhat Ansible extension (can anyone get it to work) ?
I think we found the bug as https://github.com/ansible/ansible-language-server/issues/117
nvim-lspconfig
-
JetBrains' unremovable AI assistant meets irresistible outcry
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.
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
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...
-
A guide on Neovim's LSP client
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.
-
Do I need NeoVIM?
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.
-
cpp setting problem
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.
-
Need help to set up the pbkit language server
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:
-
Option omnifunc is not set
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:
-
Using nvim-lint as a null-ls alternative for linters
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.
-
The Future of the Vim Project
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.
-
SQL LSP dialect
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.
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
jupyterlab-lsp - Coding assistance for JupyterLab (code navigation + hover suggestions + linters + autocompletion + rename) using Language Server Protocol
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
nvim-jdtls - Extensions for the built-in LSP support in Neovim for eclipse.jdt.ls
ansible-navigator - A text-based user interface (TUI) for Ansible.
coc - Chroniques Oubliées Contemporain
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible-community/ansible-lint]
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support