RepoMirrors/nvim-lspconfig
1
0
Fork 0
mirror of https://github.com/neovim/nvim-lspconfig synced 2025-03-11 04:27:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
401237e83b
nvim-lspconfig/doc/configs.md

12294 lines
283 KiB
Markdown
Raw Normal View History

docs: update configs.md skip-checks: true
2024-10-01 12:39:24 +00:00
# LSP configs
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
<!-- *lspconfig-all* *lspconfig-server-configurations* -->
docs: update configs.md skip-checks: true
2024-10-01 12:39:24 +00:00
LSP configurations provided by nvim-lspconfig are listed below. This
documentation is autogenerated from the Lua files. You can view this file in
Nvim by running `:help lspconfig-all`.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-24 11:47:53 +00:00
- [ada_ls](#ada_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [agda_ls](#agda_ls)
- [aiken](#aiken)
- [anakin_language_server](#anakin_language_server)
- [angularls](#angularls)
- [ansiblels](#ansiblels)
- [antlersls](#antlersls)
- [apex_ls](#apex_ls)
- [arduino_language_server](#arduino_language_server)
- [asm_lsp](#asm_lsp)
- [ast_grep](#ast_grep)
- [astro](#astro)
docs: update configs.md skip-checks: true
2025-01-05 08:34:03 +00:00
- [atlas](#atlas)
docs: update configs.md skip-checks: true
2024-12-22 23:46:11 +00:00
- [autohotkey_lsp](#autohotkey_lsp)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [autotools_ls](#autotools_ls)
- [awk_ls](#awk_ls)
- [azure_pipelines_ls](#azure_pipelines_ls)
- [bacon_ls](#bacon_ls)
- [ballerina](#ballerina)
- [basedpyright](#basedpyright)
- [bashls](#bashls)
docs: update configs.md skip-checks: true
2024-10-09 05:22:56 +00:00
- [basics_ls](#basics_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [bazelrc_lsp](#bazelrc_lsp)
- [beancount](#beancount)
- [bicep](#bicep)
- [biome](#biome)
- [bitbake_language_server](#bitbake_language_server)
- [bitbake_ls](#bitbake_ls)
- [blueprint_ls](#blueprint_ls)
- [bqnlsp](#bqnlsp)
- [bright_script](#bright_script)
- [bsl_ls](#bsl_ls)
- [buck2](#buck2)
- [buddy_ls](#buddy_ls)
docs: update configs.md skip-checks: true
2024-11-06 05:39:04 +00:00
- [buf_ls](#buf_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [bufls](#bufls)
- [bzl](#bzl)
- [c3_lsp](#c3_lsp)
- [cadence](#cadence)
- [cairo_ls](#cairo_ls)
- [ccls](#ccls)
- [cds_lsp](#cds_lsp)
- [circom-lsp](#circom-lsp)
- [clangd](#clangd)
- [clarity_lsp](#clarity_lsp)
- [clojure_lsp](#clojure_lsp)
- [cmake](#cmake)
- [cobol_ls](#cobol_ls)
- [codeqlls](#codeqlls)
- [coffeesense](#coffeesense)
- [contextive](#contextive)
- [coq_lsp](#coq_lsp)
- [crystalline](#crystalline)
- [csharp_ls](#csharp_ls)
- [css_variables](#css_variables)
- [cssls](#cssls)
- [cssmodules_ls](#cssmodules_ls)
- [cucumber_language_server](#cucumber_language_server)
docs: update configs.md skip-checks: true
2024-12-29 02:27:12 +00:00
- [cue](#cue)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [custom_elements_ls](#custom_elements_ls)
- [cypher_ls](#cypher_ls)
- [daedalus_ls](#daedalus_ls)
- [dafny](#dafny)
- [dagger](#dagger)
- [dartls](#dartls)
- [dcmls](#dcmls)
- [debputy](#debputy)
- [delphi_ls](#delphi_ls)
- [denols](#denols)
- [dhall_lsp_server](#dhall_lsp_server)
- [diagnosticls](#diagnosticls)
- [digestif](#digestif)
- [djlsp](#djlsp)
- [docker_compose_language_service](#docker_compose_language_service)
- [dockerls](#dockerls)
- [dolmenls](#dolmenls)
- [dotls](#dotls)
- [dprint](#dprint)
- [drools_lsp](#drools_lsp)
- [ds_pinyin_lsp](#ds_pinyin_lsp)
- [earthlyls](#earthlyls)
- [ecsact](#ecsact)
- [efm](#efm)
- [elixirls](#elixirls)
- [elmls](#elmls)
- [elp](#elp)
- [ember](#ember)
- [emmet_language_server](#emmet_language_server)
- [emmet_ls](#emmet_ls)
- [erg_language_server](#erg_language_server)
- [erlangls](#erlangls)
- [esbonio](#esbonio)
- [eslint](#eslint)
- [facility_language_server](#facility_language_server)
- [fennel_language_server](#fennel_language_server)
- [fennel_ls](#fennel_ls)
- [fish_lsp](#fish_lsp)
- [flow](#flow)
- [flux_lsp](#flux_lsp)
- [foam_ls](#foam_ls)
- [fortls](#fortls)
- [fsautocomplete](#fsautocomplete)
- [fsharp_language_server](#fsharp_language_server)
- [fstar](#fstar)
- [futhark_lsp](#futhark_lsp)
- [gdscript](#gdscript)
- [gdshader_lsp](#gdshader_lsp)
docs: update configs.md skip-checks: true
2025-01-13 08:40:59 +00:00
- [gh_actions_ls](#gh_actions_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [ghcide](#ghcide)
- [ghdl_ls](#ghdl_ls)
- [ginko_ls](#ginko_ls)
- [gitlab_ci_ls](#gitlab_ci_ls)
- [glasgow](#glasgow)
- [gleam](#gleam)
- [glint](#glint)
- [glsl_analyzer](#glsl_analyzer)
- [glslls](#glslls)
- [golangci_lint_ls](#golangci_lint_ls)
- [gopls](#gopls)
- [gradle_ls](#gradle_ls)
- [grammarly](#grammarly)
- [graphql](#graphql)
- [groovyls](#groovyls)
- [guile_ls](#guile_ls)
- [harper_ls](#harper_ls)
- [haxe_language_server](#haxe_language_server)
- [hdl_checker](#hdl_checker)
- [helm_ls](#helm_ls)
- [hhvm](#hhvm)
- [hie](#hie)
- [hlasm](#hlasm)
- [hls](#hls)
- [hoon_ls](#hoon_ls)
- [html](#html)
- [htmx](#htmx)
- [hydra_lsp](#hydra_lsp)
- [hyprls](#hyprls)
- [idris2_lsp](#idris2_lsp)
- [intelephense](#intelephense)
- [janet_lsp](#janet_lsp)
- [java_language_server](#java_language_server)
- [jdtls](#jdtls)
- [jedi_language_server](#jedi_language_server)
- [jinja_lsp](#jinja_lsp)
- [jqls](#jqls)
- [jsonls](#jsonls)
- [jsonnet_ls](#jsonnet_ls)
- [julials](#julials)
- [kcl](#kcl)
- [koka](#koka)
- [kotlin_language_server](#kotlin_language_server)
docs: update configs.md skip-checks: true
2024-10-07 05:17:58 +00:00
- [kulala_ls](#kulala_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [lean3ls](#lean3ls)
- [leanls](#leanls)
- [lelwel_ls](#lelwel_ls)
- [lemminx](#lemminx)
- [lexical](#lexical)
docs: update configs.md skip-checks: true
2024-10-09 08:28:36 +00:00
- [lsp_ai](#lsp_ai)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [ltex](#ltex)
docs: update configs.md skip-checks: true
2024-12-07 13:10:51 +00:00
- [ltex_plus](#ltex_plus)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [lua_ls](#lua_ls)
- [luau_lsp](#luau_lsp)
- [lwc_ls](#lwc_ls)
- [m68k](#m68k)
- [markdown_oxide](#markdown_oxide)
docs: update configs.md skip-checks: true
2024-10-04 05:36:35 +00:00
- [marko-js](#marko-js)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [marksman](#marksman)
- [matlab_ls](#matlab_ls)
- [mdx_analyzer](#mdx_analyzer)
- [mesonlsp](#mesonlsp)
- [metals](#metals)
- [millet](#millet)
- [mint](#mint)
- [mlir_lsp_server](#mlir_lsp_server)
- [mlir_pdll_lsp_server](#mlir_pdll_lsp_server)
- [mm0_ls](#mm0_ls)
- [mojo](#mojo)
- [motoko_lsp](#motoko_lsp)
- [move_analyzer](#move_analyzer)
- [msbuild_project_tools_server](#msbuild_project_tools_server)
- [mutt_ls](#mutt_ls)
- [nelua_lsp](#nelua_lsp)
- [neocmake](#neocmake)
docs: update configs.md skip-checks: true
2024-11-07 11:25:46 +00:00
- [nextflow_ls](#nextflow_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [nextls](#nextls)
- [nginx_language_server](#nginx_language_server)
- [nickel_ls](#nickel_ls)
- [nil_ls](#nil_ls)
- [nim_langserver](#nim_langserver)
- [nimls](#nimls)
- [nixd](#nixd)
- [nomad_lsp](#nomad_lsp)
- [ntt](#ntt)
- [nushell](#nushell)
- [nxls](#nxls)
- [ocamlls](#ocamlls)
- [ocamllsp](#ocamllsp)
- [ols](#ols)
- [omnisharp](#omnisharp)
- [opencl_ls](#opencl_ls)
- [openedge_ls](#openedge_ls)
- [openscad_ls](#openscad_ls)
- [openscad_lsp](#openscad_lsp)
- [pact_ls](#pact_ls)
- [pasls](#pasls)
- [pbls](#pbls)
- [perlls](#perlls)
- [perlnavigator](#perlnavigator)
- [perlpls](#perlpls)
- [pest_ls](#pest_ls)
- [phan](#phan)
- [phpactor](#phpactor)
- [pico8_ls](#pico8_ls)
- [pkgbuild_language_server](#pkgbuild_language_server)
- [please](#please)
docs: update configs.md skip-checks: true
2024-10-12 05:26:19 +00:00
- [poryscript_pls](#poryscript_pls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [postgres_lsp](#postgres_lsp)
- [powershell_es](#powershell_es)
- [prismals](#prismals)
- [prolog_ls](#prolog_ls)
- [prosemd_lsp](#prosemd_lsp)
- [protols](#protols)
- [psalm](#psalm)
- [pug](#pug)
- [puppet](#puppet)
- [purescriptls](#purescriptls)
- [pylsp](#pylsp)
- [pylyzer](#pylyzer)
- [pyre](#pyre)
- [pyright](#pyright)
- [qml_lsp](#qml_lsp)
- [qmlls](#qmlls)
- [quick_lint_js](#quick_lint_js)
- [r_language_server](#r_language_server)
- [racket_langserver](#racket_langserver)
- [raku_navigator](#raku_navigator)
- [reason_ls](#reason_ls)
- [regal](#regal)
- [regols](#regols)
- [relay_lsp](#relay_lsp)
- [remark_ls](#remark_ls)
- [rescriptls](#rescriptls)
- [rls](#rls)
- [rnix](#rnix)
docs: update configs.md skip-checks: true
2024-11-12 08:46:09 +00:00
- [robotcode](#robotcode)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [robotframework_ls](#robotframework_ls)
- [roc_ls](#roc_ls)
- [rome](#rome)
- [rubocop](#rubocop)
- [ruby_lsp](#ruby_lsp)
- [ruff](#ruff)
- [ruff_lsp](#ruff_lsp)
- [rune_languageserver](#rune_languageserver)
- [rust_analyzer](#rust_analyzer)
- [salt_ls](#salt_ls)
- [scheme_langserver](#scheme_langserver)
- [scry](#scry)
docs: update configs.md skip-checks: true
2025-01-13 07:41:33 +00:00
- [selene3p_ls](#selene3p_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [serve_d](#serve_d)
- [shopify_theme_ls](#shopify_theme_ls)
- [sixtyfps](#sixtyfps)
- [slangd](#slangd)
- [slint_lsp](#slint_lsp)
- [smarty_ls](#smarty_ls)
- [smithy_ls](#smithy_ls)
- [snakeskin_ls](#snakeskin_ls)
- [snyk_ls](#snyk_ls)
- [solang](#solang)
- [solargraph](#solargraph)
- [solc](#solc)
- [solidity](#solidity)
- [solidity_ls](#solidity_ls)
- [solidity_ls_nomicfoundation](#solidity_ls_nomicfoundation)
- [somesass_ls](#somesass_ls)
- [sorbet](#sorbet)
- [sourcekit](#sourcekit)
- [sourcery](#sourcery)
- [spectral](#spectral)
- [spyglassmc_language_server](#spyglassmc_language_server)
- [sqlls](#sqlls)
- [sqls](#sqls)
- [standardrb](#standardrb)
- [starlark_rust](#starlark_rust)
- [starpls](#starpls)
- [statix](#statix)
- [steep](#steep)
- [stimulus_ls](#stimulus_ls)
- [stylelint_lsp](#stylelint_lsp)
docs: update configs.md skip-checks: true
2025-01-13 07:41:33 +00:00
- [stylua3p_ls](#stylua3p_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [superhtml](#superhtml)
- [svelte](#svelte)
- [svlangserver](#svlangserver)
- [svls](#svls)
- [swift_mesonls](#swift_mesonls)
- [syntax_tree](#syntax_tree)
- [tabby_ml](#tabby_ml)
- [tailwindcss](#tailwindcss)
- [taplo](#taplo)
- [tblgen_lsp_server](#tblgen_lsp_server)
- [teal_ls](#teal_ls)
- [templ](#templ)
- [terraform_lsp](#terraform_lsp)
- [terraformls](#terraformls)
- [texlab](#texlab)
- [textlsp](#textlsp)
- [tflint](#tflint)
- [theme_check](#theme_check)
- [thriftls](#thriftls)
- [tilt_ls](#tilt_ls)
- [tinymist](#tinymist)
- [ts_ls](#ts_ls)
docs: update configs.md skip-checks: true
2024-10-26 00:16:03 +00:00
- [ts_query_ls](#ts_query_ls)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [tsp_server](#tsp_server)
- [ttags](#ttags)
- [turtle_ls](#turtle_ls)
- [tvm_ffi_navigator](#tvm_ffi_navigator)
- [twiggy_language_server](#twiggy_language_server)
- [typeprof](#typeprof)
- [typos_lsp](#typos_lsp)
- [typst_lsp](#typst_lsp)
- [uiua](#uiua)
docs: update configs.md skip-checks: true
2024-10-04 06:39:10 +00:00
- [ungrammar_languageserver](#ungrammar_languageserver)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [unison](#unison)
- [unocss](#unocss)
- [uvls](#uvls)
- [v_analyzer](#v_analyzer)
- [vacuum](#vacuum)
- [vala_ls](#vala_ls)
- [vale_ls](#vale_ls)
- [vdmj](#vdmj)
- [verible](#verible)
- [veridian](#veridian)
- [veryl_ls](#veryl_ls)
- [vhdl_ls](#vhdl_ls)
- [vimls](#vimls)
- [visualforce_ls](#visualforce_ls)
- [vls](#vls)
- [volar](#volar)
docs: update configs.md skip-checks: true
2024-10-02 05:44:07 +00:00
- [vscoqtop](#vscoqtop)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- [vtsls](#vtsls)
- [vuels](#vuels)
- [wgsl_analyzer](#wgsl_analyzer)
- [yamlls](#yamlls)
- [yang_lsp](#yang_lsp)
- [yls](#yls)
- [ziggy](#ziggy)
- [ziggy_schema](#ziggy_schema)
- [zk](#zk)
- [zls](#zls)
docs: update configs.md skip-checks: true
2024-10-24 11:47:53 +00:00
## ada_ls
https://github.com/AdaCore/ada_language_server
Installation instructions can be found [here](https://github.com/AdaCore/ada_language_server#Install).
Can be configured by passing a "settings" object to `ada_ls.setup{}`:
```lua
require('lspconfig').ada_ls.setup{
settings = {
ada = {
projectFile = "project.gpr";
scenarioVariables = { ... };
}
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-24 11:47:53 +00:00
```lua
require'lspconfig'.ada_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ada_language_server" }
```
- `filetypes` :
```lua
{ "ada" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ada_ls.lua:4](../lua/lspconfig/configs/ada_ls.lua#L4)
docs: update configs.md skip-checks: true
2024-10-24 11:47:53 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## agda_ls
https://github.com/agda/agda-language-server
Language Server for Agda.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.agda_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "als" }
```
- `filetypes` :
```lua
{ "agda" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/agda_ls.lua:4](../lua/lspconfig/configs/agda_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## aiken
https://github.com/aiken-lang/aiken
A language server for Aiken Programming Language.
[Installation](https://aiken-lang.org/installation-instructions)
It can be i
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.aiken.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "aiken", "lsp" }
```
- `filetypes` :
```lua
{ "aiken" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/aiken.lua:4](../lua/lspconfig/configs/aiken.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## anakin_language_server
https://pypi.org/project/anakin-language-server/
`anakin-language-server` is yet another Jedi Python language server.
Available options:
* Initialization: https://github.com/muffinmad/anakin-language-server#initialization-option
* Configuration: https://github.com/muffinmad/anakin-language-server#configuration-options
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.anakin_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "anakinls" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/anakin_language_server.lua:4](../lua/lspconfig/configs/anakin_language_server.lua#L4)
- `settings` :
```lua
{
anakinls = {
pyflakes_errors = { "ImportStarNotPermitted", "UndefinedExport", "UndefinedLocal", "UndefinedName", "DuplicateArgument", "MultiValueRepeatedKeyLiteral", "MultiValueRepeatedKeyVariable", "FutureFeatureNotDefined", "LateFutureImport", "ReturnOutsideFunction", "YieldOutsideFunction", "ContinueOutsideLoop", "BreakOutsideLoop", "TwoStarredExpressions", "TooManyExpressionsInStarredAssignment", "ForwardAnnotationSyntaxError", "RaiseNotImplemented", "StringDotFormatExtraPositionalArguments", "StringDotFormatExtraNamedArguments", "StringDotFormatMissingArgument", "StringDotFormatMixingAutomatic", "StringDotFormatInvalidFormat", "PercentFormatInvalidFormat", "PercentFormatMixedPositionalAndNamed", "PercentFormatUnsupportedFormat", "PercentFormatPositionalCountMismatch", "PercentFormatExtraNamedArguments", "PercentFormatMissingArgument", "PercentFormatExpectedMapping", "PercentFormatExpectedSequence", "PercentFormatStarRequiresSequence" }
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## angularls
https://github.com/angular/vscode-ng-language-service
`angular-language-server` can be installed via npm `npm install -g @angular/language-server`.
Note, that if you override the default `cmd`, you must also update `on_new_config` to set `new_config.cmd` during startup.
```lua
local project_library_path = "/path/to/project/lib"
local cmd = {"ngserver", "--stdio", "--tsProbeLocations", project_library_path , "--ngProbeLocations", project_library_path}
require'lspconfig'.angularls.setup{
cmd = cmd,
on_new_config = function(new_config,new_root_dir)
new_config.cmd = cmd
end,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.angularls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ngserver", "--stdio", "--tsProbeLocations", "", "--ngProbeLocations", "" }
```
- `filetypes` :
```lua
{ "typescript", "html", "typescriptreact", "typescript.tsx", "htmlangular" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/angularls.lua:15](../lua/lspconfig/configs/angularls.lua#L15)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ansiblels
https://github.com/ansible/vscode-ansible
Language server for the ansible configuration management tool.
`ansible-language-server` can be installed via `npm`:
```sh
npm install -g @ansible/ansible-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ansiblels.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ansible-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "yaml.ansible" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ansiblels.lua:4](../lua/lspconfig/configs/ansiblels.lua#L4)
- `settings` :
```lua
{
ansible = {
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
ansible = {
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
path = "ansible"
},
executionEnvironment = {
enabled = false
},
python = {
interpreterPath = "python"
},
validation = {
enabled = true,
lint = {
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
enabled = true,
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
path = "ansible-lint"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## antlersls
https://www.npmjs.com/package/antlers-language-server
`antlersls` can be installed via `npm`:
```sh
npm install -g antlers-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.antlersls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "antlersls", "--stdio" }
```
- `filetypes` :
```lua
{ "html", "antlers" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/antlersls.lua:4](../lua/lspconfig/configs/antlersls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## apex_ls
https://github.com/forcedotcom/salesforcedx-vscode
Language server for Apex.
For manual installation, download the JAR file from the [VSCode
extension](https://github.com/forcedotcom/salesforcedx-vscode/tree/develop/packages/salesforcedx-vscode-apex).
```lua
require'lspconfig'.apex_ls.setup {
apex_jar_path = '/path/to/apex-jorje-lsp.jar',
apex_enable_semantic_errors = false, -- Whether to allow Apex Language Server to surface semantic errors
apex_enable_completion_statistics = false, -- Whether to allow Apex Language Server to collect telemetry on code completion usage
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.apex_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "apexcode" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/apex_ls.lua:4](../lua/lspconfig/configs/apex_ls.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/apex_ls.lua:4](../lua/lspconfig/configs/apex_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## arduino_language_server
https://github.com/arduino/arduino-language-server
Language server for Arduino
The `arduino-language-server` can be installed by running:
```
go install github.com/arduino/arduino-language-server@latest
```
The `arduino-cli` tool must also be installed. Follow [these
installation instructions](https://arduino.github.io/arduino-cli/latest/installation/) for
your platform.
After installing `arduino-cli`, follow [these
instructions](https://arduino.github.io/arduino-cli/latest/getting-started/#create-a-configuration-file)
for generating a configuration file if you haven't done so already, and make
sure you [install any relevant platforms
libraries](https://arduino.github.io/arduino-cli/latest/getting-started/#install-the-core-for-your-board).
The language server also requires `clangd` to be installed. Follow [these
installation instructions](https://clangd.llvm.org/installation) for your
platform.
If you don't have a sketch yet create one.
```sh
$ arduino-cli sketch new test
$ cd test
```
You will need a `sketch.yaml` file in order for the language server to understand your project. It will also save you passing options to `arduino-cli` each time you compile or upload a file. You can generate the file by using the following commands.
First gather some information about your board. Make sure your board is connected and run the following:
```sh
$ arduino-cli board list
Port Protocol Type Board Name FQBN Core
/dev/ttyACM0 serial Serial Port (USB) Arduino Uno arduino:avr:uno arduino:avr
```
Then generate the file:
```sh
arduino-cli board attach -p /dev/ttyACM0 -b arduino:avr:uno test.ino
```
The resulting file should look like this:
```yaml
default_fqbn: arduino:avr:uno
default_port: /dev/ttyACM0
```
Your folder structure should look like this:
```
.
├── test.ino
└── sketch.yaml
```
For further instructions about configuration options, run `arduino-language-server --help`.
Note that an upstream bug makes keywords in some cases become undefined by the language server.
Ref: https://github.com/arduino/arduino-ide/issues/159
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.arduino_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
textDocument = {
semanticTokens = vim.NIL
},
workspace = {
semanticTokens = vim.NIL
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "arduino-language-server" }
```
- `filetypes` :
```lua
{ "arduino" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/arduino_language_server.lua:4](../lua/lspconfig/configs/arduino_language_server.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## asm_lsp
https://github.com/bergercookie/asm-lsp
Language Server for GAS/GO Assembly
`asm-lsp` can be installed via cargo:
cargo install asm-lsp
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.asm_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "asm-lsp" }
```
- `filetypes` :
```lua
{ "asm", "vmasm" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/asm_lsp.lua:2](../lua/lspconfig/configs/asm_lsp.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ast_grep
https://ast-grep.github.io/
ast-grep(sg) is a fast and polyglot tool for code structural search, lint, rewriting at large scale.
ast-grep LSP only works in projects that have `sgconfig.y[a]ml` in their root directories.
```sh
npm install [-g] @ast-grep/cli
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ast_grep.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ast-grep", "lsp" }
```
- `filetypes` :
```lua
{ "c", "cpp", "rust", "go", "java", "python", "javascript", "typescript", "html", "css", "kotlin", "dart", "lua" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ast_grep.lua:4](../lua/lspconfig/configs/ast_grep.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## astro
https://github.com/withastro/language-tools/tree/main/packages/language-server
`astro-ls` can be installed via `npm`:
```sh
npm install -g @astrojs/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.astro.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "astro-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "astro" }
```
- `init_options` :
```lua
{
typescript = {}
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/astro.lua:9](../lua/lspconfig/configs/astro.lua#L9)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/astro.lua:9](../lua/lspconfig/configs/astro.lua#L9)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2025-01-05 08:34:03 +00:00
## atlas
https://github.com/ariga/atlas
Language server for Atlas config and scheme files.
You may also need to configure the filetype for *.hcl files:
`autocmd BufNewFile,BufRead atlas.hcl set filetype=atlas-config`
`autocmd BufNewFile,BufRead *.my.hcl set filetype=atlas-schema-mysql`
`autocmd BufNewFile,BufRead *.pg.hcl set filetype=atlas-schema-postgresql`
`autocmd BufNewFile,BufRead *.lt.hcl set filetype=atlas-schema-sqlite`
`autocmd BufNewFile,BufRead *.ch.hcl set filetype=atlas-schema-clickhouse`
`autocmd BufNewFile,BufRead *.ms.hcl set filetype=atlas-schema-mssql`
`autocmd BufNewFile,BufRead *.rs.hcl set filetype=atlas-schema-redshift`
`autocmd BufNewFile,BufRead *.test.hcl set filetype=atlas-test`
`autocmd BufNewFile,BufRead *.plan.hcl set filetype=atlas-plan`
or
```lua
vim.filetype.add({
filename = {
['atlas.hcl'] = 'atlas-config',
},
pattern = {
['.*/*.my.hcl'] = 'atlas-schema-mysql',
['.*/*.pg.hcl'] = 'atlas-schema-postgresql',
['.*/*.lt.hcl'] = 'atlas-schema-sqlite',
['.*/*.ch.hcl'] = 'atlas-schema-clickhouse',
['.*/*.ms.hcl'] = 'atlas-schema-mssql',
['.*/*.rs.hcl'] = 'atlas-schema-redshift',
['.*/*.test.hcl'] = 'atlas-test',
['.*/*.plan.hcl'] = 'atlas-plan',
},
})
```
Snippet to enable the language server:
```lua
require'lspconfig'.atlas.setup{}
```
Default config:
- `cmd` :
```lua
{ "atlas", "tool", "lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "atlas-*" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/atlas.lua:4](../lua/lspconfig/configs/atlas.lua#L4)
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-12-22 23:46:11 +00:00
## autohotkey_lsp
https://github.com/thqby/vscode-autohotkey2-lsp
AutoHotkey v2.0 LSP implementation
Snippet to enable the language server:
```lua
require'lspconfig'.autohotkey_lsp.setup{}
```
Default config:
- `autostart` : `true`
- `cmd` :
```lua
{ "autohotkey_lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "autohotkey" }
```
- `flags` :
```lua
{
debounce_text_changes = 500
}
```
- `init_options` :
```lua
{
ActionWhenV1IsDetected = "Continue",
AutoLibInclude = "All",
CommentTags = "^;;\\s*(?<tag>.+)",
CompleteFunctionParens = false,
Diagnostics = {
ClassStaticMemberCheck = true,
ParamsCheck = true
},
FormatOptions = {
array_style = "expand",
brace_style = "One True Brace",
break_chained_methods = false,
ignore_comment = false,
indent_string = "\t",
max_preserve_newlines = 2,
object_style = "none",
preserve_newlines = true,
space_after_double_colon = true,
space_before_conditional = true,
space_in_empty_paren = false,
space_in_other = true,
space_in_paren = false,
wrap_line_length = 0
},
InterpreterPath = "",
SymbolFoldinFromOpenBrace = false,
locale = "en-us"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/autohotkey_lsp.lua:8](../lua/lspconfig/configs/autohotkey_lsp.lua#L8)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## autotools_ls
https://github.com/Freed-Wu/autotools-language-server
`autotools-language-server` can be installed via `pip`:
```sh
pip install autotools-language-server
```
Language server for autoconf, automake and make using tree sitter in python.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.autotools_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "autotools-language-server" }
```
- `filetypes` :
```lua
{ "config", "automake", "make" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/autotools_ls.lua:6](../lua/lspconfig/configs/autotools_ls.lua#L6)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## awk_ls
https://github.com/Beaglefoot/awk-language-server/
`awk-language-server` can be installed via `npm`:
```sh
npm install -g awk-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.awk_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "awk-language-server" }
```
- `filetypes` :
```lua
{ "awk" }
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## azure_pipelines_ls
https://github.com/microsoft/azure-pipelines-language-server
An Azure Pipelines language server
`azure-pipelines-ls` can be installed via `npm`:
```sh
npm install -g azure-pipelines-language-server
```
By default `azure-pipelines-ls` will only work in files named `azure-pipelines.yml`, this can be changed by providing additional settings like so:
```lua
require("lspconfig").azure_pipelines_ls.setup {
... -- other configuration for setup {}
settings = {
yaml = {
schemas = {
["https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json"] = {
"/azure-pipeline*.y*l",
"/*.azure*",
"Azure-Pipelines/**/*.y*l",
"Pipelines/*.y*l",
},
},
},
},
}
```
The Azure Pipelines LSP is a fork of `yaml-language-server` and as such the same settings can be passed to it as `yaml-language-server`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.azure_pipelines_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "azure-pipelines-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "yaml" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/azure_pipelines_ls.lua:4](../lua/lspconfig/configs/azure_pipelines_ls.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bacon_ls
https://github.com/crisidev/bacon-ls
A Language Server Protocol wrapper for [bacon](https://dystroy.org/bacon/).
It offers textDocument/diagnostic and workspace/diagnostic capabilities for Rust
workspaces using the Bacon export locations file.
It requires `bacon` and `bacon-ls` to be installed on the system using
[mason.nvim](https://github.com/williamboman/mason.nvim) or manually:util
```sh
$ cargo install --locked bacon bacon-ls
```
Settings can be changed using the `settings` dictionary:util
```lua
settings = {
-- Bacon export filename, default .bacon-locations
locationsFile = ".bacon-locations",
-- Maximum time in seconds the LSP server waits for Bacon to update the
-- export file before loading the new diagnostics
waitTimeSeconds = 10
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bacon_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bacon-ls" }
```
- `filetypes` :
```lua
{ "rust" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bacon_ls.lua:4](../lua/lspconfig/configs/bacon_ls.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ballerina
Ballerina language server
The Ballerina language's CLI tool comes with its own language server implementation.
The `bal` command line tool must be installed and available in your system's PATH.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ballerina.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bal", "start-language-server" }
```
- `filetypes` :
```lua
{ "ballerina" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ballerina.lua:4](../lua/lspconfig/configs/ballerina.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## basedpyright
https://detachhead.github.io/basedpyright
`basedpyright`, a static type checker and language server for python
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.basedpyright.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- PyrightOrganizeImports: Organize Imports
- PyrightSetPythonPath: Reconfigure basedpyright with the provided python path
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "basedpyright-langserver", "--stdio" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/basedpyright.lua:44](../lua/lspconfig/configs/basedpyright.lua#L44)
- `settings` :
```lua
{
basedpyright = {
analysis = {
autoSearchPaths = true,
diagnosticMode = "openFilesOnly",
useLibraryCodeForTypes = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bashls
https://github.com/bash-lsp/bash-language-server
`bash-language-server` can be installed via `npm`:
```sh
npm i -g bash-language-server
```
Language server for bash, written using tree sitter in typescript.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bashls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bash-language-server", "start" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-11-28 05:48:59 +00:00
{ "bash", "sh" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bashls.lua:2](../lua/lspconfig/configs/bashls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
bashIde = {
globPattern = "*@(.sh|.inc|.bash|.command)"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-09 05:22:56 +00:00
## basics_ls
https://github.com/antonk52/basics-language-server/
Buffer, path, and snippet completion
```sh
npm install -g basics-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-09 05:22:56 +00:00
```lua
require'lspconfig'.basics_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "basics-language-server" }
```
- `settings` :
```lua
{
buffer = {
enable = true,
minCompletionLength = 4
},
path = {
enable = true
},
snippet = {
enable = false,
sources = {}
docs: update configs.md skip-checks: true
2024-10-09 05:22:56 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-09 05:22:56 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bazelrc_lsp
https://github.com/salesforce-misc/bazelrc-lsp
`bazelrc-lsp` is a LSP for `.bazelrc` configuration files.
The `.bazelrc` file type is not detected automatically, you can register it manually (see below) or override the filetypes:
```lua
vim.filetype.add {
pattern = {
['.*.bazelrc'] = 'bazelrc',
},
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bazelrc_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bazelrc-lsp" }
```
- `filetypes` :
```lua
{ "bazelrc" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bazelrc_lsp.lua:4](../lua/lspconfig/configs/bazelrc_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## beancount
https://github.com/polarmutex/beancount-language-server#installation
See https://github.com/polarmutex/beancount-language-server#configuration for configuration options
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.beancount.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "beancount-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "beancount", "bean" }
```
- `init_options` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/beancount.lua:2](../lua/lspconfig/configs/beancount.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bicep
https://github.com/azure/bicep
Bicep language server
Bicep language server can be installed by downloading and extracting a release of bicep-langserver.zip from [Bicep GitHub releases](https://github.com/Azure/bicep/releases).
Bicep language server requires the [dotnet-sdk](https://dotnet.microsoft.com/download) to be installed.
Neovim does not have built-in support for the bicep filetype which is required for lspconfig to automatically launch the language server.
Filetype detection can be added via an autocmd:
```lua
vim.cmd [[ autocmd BufNewFile,BufRead *.bicep set filetype=bicep ]]
```
**By default, bicep language server does not have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set `cmd` to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.
```lua
local bicep_lsp_bin = "/path/to/bicep-langserver/Bicep.LangServer.dll"
require'lspconfig'.bicep.setup{
cmd = { "dotnet", bicep_lsp_bin };
...
}
```
To download the latest release and place in /usr/local/bin/bicep-langserver:
```bash
(cd $(mktemp -d) \
&& curl -fLO https://github.com/Azure/bicep/releases/latest/download/bicep-langserver.zip \
&& rm -rf /usr/local/bin/bicep-langserver \
&& unzip -d /usr/local/bin/bicep-langserver bicep-langserver.zip)
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bicep.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "bicep" }
```
- `init_options` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bicep.lua:2](../lua/lspconfig/configs/bicep.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## biome
https://biomejs.dev
Toolchain of the web. [Successor of Rome](https://biomejs.dev/blog/annoucing-biome).
```sh
npm install [-g] @biomejs/biome
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.biome.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "biome", "lsp-proxy" }
```
- `filetypes` :
```lua
{ "astro", "css", "graphql", "javascript", "javascriptreact", "json", "jsonc", "svelte", "typescript", "typescript.tsx", "typescriptreact", "vue" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/biome.lua:4](../lua/lspconfig/configs/biome.lua#L4)
- `single_file_support` : `false`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bitbake_language_server
🛠️ bitbake language server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bitbake_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bitbake-language-server" }
```
- `filetypes` :
```lua
{ "bitbake" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bitbake_language_server.lua:2](../lua/lspconfig/configs/bitbake_language_server.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bitbake_ls
https://github.com/yoctoproject/vscode-bitbake/tree/staging/server
https://www.npmjs.com/package/language-server-bitbake
Official Bitbake Language Server for the Yocto Project.
Can be installed from npm or github.
```
npm install -g language-server-bitbake
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bitbake_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "language-server-bitbake", "--stdio" }
```
- `filetypes` :
```lua
{ "bitbake" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bitbake_ls.lua:2](../lua/lspconfig/configs/bitbake_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `false`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## blueprint_ls
https://gitlab.gnome.org/jwestman/blueprint-compiler
`blueprint-compiler` can be installed via your system package manager.
Language server for the blueprint markup language, written in python and part
of the blueprint-compiler.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.blueprint_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "blueprint-compiler", "lsp" }
```
- `cmd_env` :
```lua
{
GLOB_PATTERN = "*@(.blp)"
}
```
- `filetypes` :
```lua
{ "blueprint" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/blueprint_ls.lua:2](../lua/lspconfig/configs/blueprint_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bqnlsp
https://git.sr.ht/~detegr/bqnlsp
`bqnlsp`, a language server for BQN.
The binary depends on the shared library of [CBQN](https://github.com/dzaima/CBQN) `libcbqn.so`.
If CBQN is installed system-wide (using `sudo make install` in its source directory) and `bqnlsp` errors that it can't find the shared library, update the linker cache by executing `sudo ldconfig`.
If CBQN has been installed in a non-standard directory or can't be installed globally pass `libcbqnPath = '/path/to/CBQN'` to the setup function.
This will set the environment variables `LD_LIBRARY_PATH` (Linux) or `DYLD_LIBRARY_PATH` (macOS) to the provided path.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bqnlsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bqnlsp" }
```
- `filetypes` :
```lua
{ "bqn" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/bqnlsp.lua:14](../lua/lspconfig/configs/bqnlsp.lua#L14)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bqnlsp.lua:14](../lua/lspconfig/configs/bqnlsp.lua#L14)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bright_script
https://github.com/RokuCommunity/brighterscript
`brightscript` can be installed via `npm`:
```sh
npm install -g brighterscript
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bright_script.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bsc", "--lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "brs" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bright_script.lua:4](../lua/lspconfig/configs/bright_script.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bsl_ls
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/1c-syntax/bsl-language-server
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
Language Server Protocol implementation for 1C (BSL) - 1C:Enterprise 8 and OneScript languages.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bsl_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "bsl", "os" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bsl_ls.lua:2](../lua/lspconfig/configs/bsl_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## buck2
https://github.com/facebook/buck2
Build system, successor to Buck
To better detect Buck2 project files, the following can be added:
```
vim.cmd [[ autocmd BufRead,BufNewFile *.bxl,BUCK,TARGETS set filetype=bzl ]]
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.buck2.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "buck2", "lsp" }
```
- `filetypes` :
```lua
{ "bzl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/buck2.lua:4](../lua/lspconfig/configs/buck2.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## buddy_ls
https://github.com/buddy-compiler/buddy-mlir#buddy-lsp-server
The Language Server for the buddy-mlir, a drop-in replacement for mlir-lsp-server,
supporting new dialects defined in buddy-mlir.
`buddy-lsp-server` can be installed at the buddy-mlir repository (buddy-compiler/buddy-mlir)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.buddy_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "buddy-lsp-server" }
```
- `filetypes` :
```lua
{ "mlir" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/buddy_ls.lua:2](../lua/lspconfig/configs/buddy_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-11-06 05:39:04 +00:00
## buf_ls
https://github.com/bufbuild/buf
buf beta lsp included in the cli itself
buf beta lsp is a Protobuf language server compatible with Buf modules and workspaces
Snippet to enable the language server:
```lua
require'lspconfig'.buf_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "buf", "beta", "lsp", "--timeout=0", "--log-format=text" }
```
- `filetypes` :
```lua
{ "proto" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/buf_ls.lua:2](../lua/lspconfig/configs/buf_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bufls
https://github.com/bufbuild/buf-language-server
`buf-language-server` can be installed via `go install`:
```sh
go install github.com/bufbuild/buf-language-server/cmd/bufls@latest
```
bufls is a Protobuf language server compatible with Buf modules and workspaces
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bufls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bufls", "serve" }
```
- `filetypes` :
```lua
{ "proto" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bufls.lua:4](../lua/lspconfig/configs/bufls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## bzl
https://bzl.io/
https://docs.stack.build/docs/cli/installation
https://docs.stack.build/docs/vscode/starlark-language-server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.bzl.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "bzl", "lsp", "serve" }
```
- `filetypes` :
```lua
{ "bzl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/bzl.lua:4](../lua/lspconfig/configs/bzl.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## c3_lsp
https://github.com/pherrymason/c3-lsp
Language Server for c3.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.c3_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "c3lsp" }
```
- `filetypes` :
```lua
{ "c3", "c3i" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/c3_lsp.lua:4](../lua/lspconfig/configs/c3_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cadence
[Cadence Language Server](https://github.com/onflow/cadence-tools/tree/master/languageserver)
using the [flow-cli](https://developers.flow.com/tools/flow-cli).
The `flow` command from flow-cli must be available. For install instructions see
[the docs](https://developers.flow.com/tools/flow-cli/install#install-the-flow-cli) or the
[Github page](https://github.com/onflow/flow-cli).
By default the configuration is taken from the closest `flow.json` or the `flow.json` in the users home directory.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cadence.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "flow", "cadence", "language-server" }
```
- `filetypes` :
```lua
{ "cdc" }
```
- `init_options` :
```lua
{
numberOfAccounts = "1"
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/cadence.lua:4](../lua/lspconfig/configs/cadence.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cadence.lua:4](../lua/lspconfig/configs/cadence.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cairo_ls
[Cairo Language Server](https://github.com/starkware-libs/cairo/tree/main/crates/cairo-lang-language-server)
First, install Cairo following [this tutorial](https://book.cairo-lang.org/ch01-01-installation.html)
Then enable Cairo Language Server in your Lua configuration.
```lua
require'lspconfig'.cairo_ls.setup{}
```
*cairo-language-server is still under active development, some features might not work yet !*
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cairo_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "scarb-cairo-language-server", "/C", "--node-ipc" }
```
- `filetypes` :
```lua
{ "cairo" }
```
- `init_options` :
```lua
{
hostInfo = "neovim"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cairo_ls.lua:4](../lua/lspconfig/configs/cairo_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ccls
https://github.com/MaskRay/ccls/wiki
ccls relies on a [JSON compilation database](https://clang.llvm.org/docs/JSONCompilationDatabase.html) specified
as compile_commands.json or, for simpler projects, a .ccls.
For details on how to automatically generate one using CMake look [here](https://cmake.org/cmake/help/latest/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html). Alternatively, you can use [Bear](https://github.com/rizsotto/Bear).
Customization options are passed to ccls at initialization time via init_options, a list of available options can be found [here](https://github.com/MaskRay/ccls/wiki/Customization#initialization-options). For example:
```lua
local lspconfig = require'lspconfig'
lspconfig.ccls.setup {
init_options = {
compilationDatabaseDirectory = "build";
index = {
threads = 0;
};
clang = {
excludeArgs = { "-frounding-math"} ;
};
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ccls.setup{}
```
docs: update configs.md skip-checks: true
2025-01-02 05:26:06 +00:00
Commands:
- CclsSwitchSourceHeader: Switch between source/header
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ccls" }
```
- `filetypes` :
```lua
{ "c", "cpp", "objc", "objcpp", "cuda" }
```
- `offset_encoding` :
```lua
"utf-32"
```
docs: update configs.md skip-checks: true
2025-01-02 07:26:49 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ccls.lua:24](../lua/lspconfig/configs/ccls.lua#L24)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `false`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cds_lsp
https://cap.cloud.sap/docs/
`cds-lsp` can be installed via `npm`:
```sh
npm i -g @sap/cds-lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cds_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cds-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "cds" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cds_lsp.lua:4](../lua/lspconfig/configs/cds_lsp.lua#L4)
- `settings` :
```lua
{
cds = {
validate = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## circom-lsp
[Circom Language Server](https://github.com/rubydusa/circom-lsp)
`circom-lsp`, the language server for the Circom language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.circom-lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "circom-lsp" }
```
- `filetypes` :
```lua
{ "circom" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/circom-lsp.lua:2](../lua/lspconfig/configs/circom-lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## clangd
https://clangd.llvm.org/installation.html
docs: fix old URL
2024-10-09 18:52:54 +00:00
- **NOTE:** Clang >= 11 is recommended! See [#23](https://github.com/neovim/nvim-lspconfig/issues/23).
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- If `compile_commands.json` lives in a build directory, you should
symlink it to the root of your source tree.
```
ln -s /path/to/myproject/build/compile_commands.json /path/to/myproject/
```
- clangd relies on a [JSON compilation database](https://clang.llvm.org/docs/JSONCompilationDatabase.html)
specified as compile_commands.json, see https://clangd.llvm.org/installation#compile_commandsjson
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.clangd.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- ClangdShowSymbolInfo: Show symbol info
- ClangdSwitchSourceHeader: Switch between source/header
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
offsetEncoding = { "utf-8", "utf-16" },
textDocument = {
completion = {
editsNearCursor = true
regen docs
2024-10-24 15:06:10 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "clangd" }
```
- `filetypes` :
```lua
{ "c", "cpp", "objc", "objcpp", "cuda", "proto" }
```
docs: update configs.md skip-checks: true
2024-11-24 00:58:53 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/clangd.lua:51](../lua/lspconfig/configs/clangd.lua#L51)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## clarity_lsp
`clarity-lsp` is a language server for the Clarity language. Clarity is a decidable smart contract language that optimizes for predictability and security. Smart contracts allow developers to encode essential business logic on a blockchain.
To learn how to configure the clarity language server, see the [clarity-lsp documentation](https://github.com/hirosystems/clarity-lsp).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.clarity_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "clarity-lsp" }
```
- `filetypes` :
```lua
{ "clar", "clarity" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/clarity_lsp.lua:4](../lua/lspconfig/configs/clarity_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## clojure_lsp
https://github.com/clojure-lsp/clojure-lsp
Clojure Language Server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.clojure_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "clojure-lsp" }
```
- `filetypes` :
```lua
{ "clojure", "edn" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/clojure_lsp.lua:4](../lua/lspconfig/configs/clojure_lsp.lua#L4)
docs: update configs.md skip-checks: true
2025-01-08 11:12:29 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cmake
https://github.com/regen100/cmake-language-server
CMake LSP Implementation
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cmake.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cmake-language-server" }
```
- `filetypes` :
```lua
{ "cmake" }
```
- `init_options` :
```lua
{
buildDirectory = "build"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cmake.lua:4](../lua/lspconfig/configs/cmake.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cobol_ls
Cobol language support
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cobol_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cobol-language-support" }
```
- `filetypes` :
```lua
{ "cobol" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cobol_ls.lua:2](../lua/lspconfig/configs/cobol_ls.lua#L2)
regen docs
2024-10-24 15:06:10 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## codeqlls
Reference:
https://codeql.github.com/docs/codeql-cli/
Binaries:
https://github.com/github/codeql-cli-binaries
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.codeqlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `before_init` source (use "gF" to visit): [../lua/lspconfig/configs/codeqlls.lua:6](../lua/lspconfig/configs/codeqlls.lua#L6)
- `cmd` :
```lua
{ "codeql", "execute", "language-server", "--check-errors", "ON_CHANGE", "-q" }
```
- `filetypes` :
```lua
{ "ql" }
```
- `log_level` :
```lua
2
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/codeqlls.lua:6](../lua/lspconfig/configs/codeqlls.lua#L6)
- `settings` :
```lua
{
search_path = vim.empty_dict()
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## coffeesense
https://github.com/phil294/coffeesense
CoffeeSense Language Server
`coffeesense-language-server` can be installed via `npm`:
```sh
npm install -g coffeesense-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.coffeesense.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "coffeesense-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "coffee" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/coffeesense.lua:4](../lua/lspconfig/configs/coffeesense.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## contextive
https://github.com/dev-cycles/contextive
Language Server for Contextive.
Contextive allows you to define terms in a central file and provides auto-completion suggestions and hover panels for these terms wherever they're used.
To install the language server, you need to download the appropriate [GitHub release asset](https://github.com/dev-cycles/contextive/releases/) for your operating system and architecture.
After the download unzip the Contextive.LanguageServer binary and copy the file into a folder that is included in your system's PATH.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.contextive.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "Contextive.LanguageServer" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/contextive.lua:4](../lua/lspconfig/configs/contextive.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## coq_lsp
https://github.com/ejgallego/coq-lsp/
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.coq_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "coq-lsp" }
```
- `filetypes` :
```lua
{ "coq" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/coq_lsp.lua:4](../lua/lspconfig/configs/coq_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## crystalline
https://github.com/elbywan/crystalline
Crystal language server.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.crystalline.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "crystalline" }
```
- `filetypes` :
```lua
{ "crystal" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/crystalline.lua:4](../lua/lspconfig/configs/crystalline.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## csharp_ls
https://github.com/razzmatazz/csharp-language-server
Language Server for C#.
csharp-ls requires the [dotnet-sdk](https://dotnet.microsoft.com/download) to be installed.
The preferred way to install csharp-ls is with `dotnet tool install --global csharp-ls`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.csharp_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "csharp-ls" }
```
- `filetypes` :
```lua
{ "cs" }
```
- `init_options` :
```lua
{
AutomaticWorkspaceInit = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/csharp_ls.lua:4](../lua/lspconfig/configs/csharp_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## css_variables
https://github.com/vunguyentuan/vscode-css-variables/tree/master/packages/css-variables-language-server
CSS variables autocompletion and go-to-definition
`css-variables-language-server` can be installed via `npm`:
```sh
npm i -g css-variables-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.css_variables.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "css-variables-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "css", "scss", "less" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/css_variables.lua:4](../lua/lspconfig/configs/css_variables.lua#L4)
- `settings` :
```lua
{
cssVariables = {
blacklistFolders = { "**/.cache", "**/.DS_Store", "**/.git", "**/.hg", "**/.next", "**/.svn", "**/bower_components", "**/CVS", "**/dist", "**/node_modules", "**/tests", "**/tmp" },
lookupFiles = { "**/*.less", "**/*.scss", "**/*.sass", "**/*.css" }
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cssls
https://github.com/hrsh7th/vscode-langservers-extracted
`css-languageserver` can be installed via `npm`:
```sh
npm i -g vscode-langservers-extracted
```
Neovim does not currently include built-in snippets. `vscode-css-language-server` only provides completions when snippet support is enabled. To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.
```lua
--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true
require'lspconfig'.cssls.setup {
capabilities = capabilities,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cssls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscode-css-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "css", "scss", "less" }
```
- `init_options` :
```lua
{
provideFormatter = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cssls.lua:4](../lua/lspconfig/configs/cssls.lua#L4)
- `settings` :
```lua
{
css = {
validate = true
},
less = {
validate = true
},
scss = {
validate = true
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cssmodules_ls
https://github.com/antonk52/cssmodules-language-server
Language server for autocompletion and go-to-definition functionality for CSS modules.
You can install cssmodules-language-server via npm:
```sh
npm install -g cssmodules-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cssmodules_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cssmodules-language-server" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "typescript", "typescriptreact" }
```
docs: update configs.md skip-checks: true
2024-12-13 13:32:03 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cssmodules_ls.lua:2](../lua/lspconfig/configs/cssmodules_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cucumber_language_server
https://cucumber.io
https://github.com/cucumber/common
https://www.npmjs.com/package/@cucumber/language-server
Language server for Cucumber.
`cucumber-language-server` can be installed via `npm`:
```sh
npm install -g @cucumber/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cucumber_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cucumber-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "cucumber" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cucumber_language_server.lua:2](../lua/lspconfig/configs/cucumber_language_server.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-29 02:27:12 +00:00
## cue
https://github.com/cue-lang/cue
CUE makes it easy to validate data, write schemas, and ensure configurations align with policies.
Snippet to enable the language server:
```lua
require'lspconfig'.cue.setup{}
```
Default config:
- `cmd` :
```lua
{ "cue", "lsp" }
```
- `filetypes` :
```lua
{ "cue" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cue.lua:4](../lua/lspconfig/configs/cue.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## custom_elements_ls
https://github.com/Matsuuu/custom-elements-language-server
`custom-elements-languageserver` depends on `typescript`. Both packages can be installed via `npm`:
```sh
npm install -g typescript custom-elements-languageserver
```
To configure typescript language server, add a
[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) or
[`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig) to the root of your
project.
Here's an example that disables type checking in JavaScript files.
```json
{
"compilerOptions": {
"module": "commonjs",
"target": "es6",
"checkJs": false
},
"exclude": [
"node_modules"
]
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.custom_elements_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "custom-elements-languageserver", "--stdio" }
```
- `init_options` :
```lua
{
hostInfo = "neovim"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/custom_elements_ls.lua:4](../lua/lspconfig/configs/custom_elements_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## cypher_ls
https://github.com/neo4j/cypher-language-support/tree/main/packages/language-server
`cypher-language-server`, language server for Cypher query language.
Part of the umbrella project cypher-language-support: https://github.com/neo4j/cypher-language-support
`cypher-language-server` can be installed via `npm`:
```sh
npm i -g @neo4j-cypher/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.cypher_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cypher-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "cypher" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/cypher_ls.lua:2](../lua/lspconfig/configs/cypher_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## daedalus_ls
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.daedalus_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "DaedalusLanguageServer" }
```
- `filetypes` :
```lua
{ "d" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/daedalus_ls.lua:14](../lua/lspconfig/configs/daedalus_ls.lua#L14)
- `settings` :
```lua
{
DaedalusLanguageServer = {
fileEncoding = "Windows-1252",
inlayHints = {
constants = true
},
loglevel = "debug",
numParserThreads = 16,
srcFileEncoding = "Windows-1252"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dafny
regen docs
2024-10-24 15:06:10 +00:00
Support for the Dafny language server.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
The default `cmd` uses "dafny server", which works on Dafny 4.0.0+. For
older versions of Dafny, you can compile the language server from source at
[dafny-lang/language-server-csharp](https://github.com/dafny-lang/language-server-csharp)
and set `cmd = {"dotnet", "<Path to your language server>"}`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dafny.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dafny", "server" }
```
- `filetypes` :
```lua
{ "dfy", "dafny" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dafny.lua:2](../lua/lspconfig/configs/dafny.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dagger
https://github.com/dagger/cuelsp
Dagger's lsp server for cuelang.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dagger.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "cuelsp" }
```
- `filetypes` :
```lua
{ "cue" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dagger.lua:4](../lua/lspconfig/configs/dagger.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dartls
https://github.com/dart-lang/sdk/tree/master/pkg/analysis_server/tool/lsp_spec
Language server for dart.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dartls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dart", "language-server", "--protocol=lsp" }
```
- `filetypes` :
```lua
{ "dart" }
```
- `init_options` :
```lua
{
closingLabels = true,
flutterOutline = true,
onlyAnalyzeProjectsWithOpenFiles = true,
outline = true,
suggestFromUnimportedLibraries = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dartls.lua:4](../lua/lspconfig/configs/dartls.lua#L4)
- `settings` :
```lua
{
dart = {
completeFunctionCalls = true,
showTodos = true
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dcmls
https://dcm.dev/
Language server for DCM analyzer.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dcmls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dcm", "start-server", "--client=neovim" }
```
- `filetypes` :
```lua
{ "dart" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dcmls.lua:4](../lua/lspconfig/configs/dcmls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## debputy
https://salsa.debian.org/debian/debputy
Language Server for Debian packages.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.debputy.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "debputy", "lsp", "server" }
```
- `filetypes` :
```lua
{ "debcontrol", "debcopyright", "debchangelog", "make", "yaml" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/debputy.lua:4](../lua/lspconfig/configs/debputy.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## delphi_ls
Language server for Delphi from Embarcadero.
https://marketplace.visualstudio.com/items?itemName=EmbarcaderoTechnologies.delphilsp
Note, the '*.delphilsp.json' file is required, more details at:
https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Using_DelphiLSP_Code_Insight_with_Other_Editors
Below, you'll find a sample configuration for the lazy manager.
When on_attach is triggered, it signals DelphiLSP to load settings from a configuration file.
Without this step, DelphiLSP initializes but remains non-functional:
```lua
"neovim/nvim-lspconfig",
lazy = false,
config = function()
local capabilities = require("cmp_nvim_lsp").default_capabilities()
local lspconfig = require("lspconfig")
lspconfig.delphi_ls.setup({
capabilities = capabilities,
on_attach = function(client)
local lsp_config = vim.fs.find(function(name)
return name:match(".*%.delphilsp.json$")
end, { type = "file", path = client.config.root_dir, upward = false })[1]
if lsp_config then
client.config.settings = { settingsFile = lsp_config }
client.notify("workspace/didChangeConfiguration", { settings = client.config.settings })
else
vim.notify_once("delphi_ls: '*.delphilsp.json' config file not found")
end
end,
})
end,
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.delphi_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "DelphiLSP.exe" }
```
- `filetypes` :
```lua
{ "pascal" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/delphi_ls.lua:4](../lua/lspconfig/configs/delphi_ls.lua#L4)
- `single_file_support` : `false`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## denols
https://github.com/denoland/deno
Deno's built-in language server
To appropriately highlight codefences returned from denols, you will need to augment vim.g.markdown_fenced languages
in your init.lua. Example:
```lua
vim.g.markdown_fenced_languages = {
"ts=typescript"
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.denols.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- DenolsCache: Cache a module and all of its dependencies.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "deno", "lsp" }
```
- `cmd_env` :
```lua
{
NO_COLOR = true
}
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
```
- `handlers` :
```lua
{
["textDocument/definition"] = <function 1>,
["textDocument/references"] = <function 1>,
["textDocument/typeDefinition"] = <function 1>
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/denols.lua:66](../lua/lspconfig/configs/denols.lua#L66)
- `settings` :
```lua
{
deno = {
enable = true,
suggest = {
imports = {
hosts = {
["https://deno.land"] = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dhall_lsp_server
https://github.com/dhall-lang/dhall-haskell/tree/master/dhall-lsp-server
language server for dhall
`dhall-lsp-server` can be installed via cabal:
```sh
cabal install dhall-lsp-server
```
prebuilt binaries can be found [here](https://github.com/dhall-lang/dhall-haskell/releases).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dhall_lsp_server.setup{}
regen docs
2024-10-24 15:06:10 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dhall-lsp-server" }
```
- `filetypes` :
```lua
{ "dhall" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dhall_lsp_server.lua:2](../lua/lspconfig/configs/dhall_lsp_server.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## diagnosticls
https://github.com/iamcco/diagnostic-languageserver
Diagnostic language server integrate with linters.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.diagnosticls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "diagnostic-languageserver", "--stdio" }
```
- `filetypes` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/diagnosticls.lua:3](../lua/lspconfig/configs/diagnosticls.lua#L3)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## digestif
https://github.com/astoff/digestif
Digestif is a code analyzer, and a language server, for LaTeX, ConTeXt et caterva. It provides
context-sensitive completion, documentation, code navigation, and related functionality to any
text editor that speaks the LSP protocol.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.digestif.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "digestif" }
```
- `filetypes` :
```lua
{ "tex", "plaintex", "context" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/digestif.lua:2](../lua/lspconfig/configs/digestif.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## djlsp
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/fourdigits/django-template-lsp
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
`djlsp`, a language server for Django templates.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.djlsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "djlsp" }
```
- `filetypes` :
```lua
{ "html", "htmldjango" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/djlsp.lua:2](../lua/lspconfig/configs/djlsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## docker_compose_language_service
https://github.com/microsoft/compose-language-service
This project contains a language service for Docker Compose.
`compose-language-service` can be installed via `npm`:
```sh
npm install @microsoft/compose-language-service
```
Note: If the docker-compose-langserver doesn't startup when entering a `docker-compose.yaml` file, make sure that the filetype is `yaml.docker-compose`. You can set with: `:set filetype=yaml.docker-compose`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.docker_compose_language_service.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "docker-compose-langserver", "--stdio" }
```
- `filetypes` :
```lua
{ "yaml.docker-compose" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/docker_compose_language_service.lua:4](../lua/lspconfig/configs/docker_compose_language_service.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dockerls
https://github.com/rcjsuen/dockerfile-language-server-nodejs
`docker-langserver` can be installed via `npm`:
```sh
npm install -g dockerfile-language-server-nodejs
```
Additional configuration can be applied in the following way:
```lua
require("lspconfig").dockerls.setup {
settings = {
docker = {
languageserver = {
formatter = {
ignoreMultilineInstructions = true,
},
},
}
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dockerls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "docker-langserver", "--stdio" }
```
- `filetypes` :
```lua
{ "dockerfile" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dockerls.lua:4](../lua/lspconfig/configs/dockerls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dolmenls
https://github.com/Gbury/dolmen/blob/master/doc/lsp.md
`dolmenls` can be installed via `opam`
```sh
opam install dolmen_lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dolmenls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dolmenls" }
```
- `filetypes` :
```lua
{ "smt2", "tptp", "p", "cnf", "icnf", "zf" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dolmenls.lua:2](../lua/lspconfig/configs/dolmenls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dotls
https://github.com/nikeee/dot-language-server
`dot-language-server` can be installed via `npm`:
```sh
npm install -g dot-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dotls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dot-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "dot" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dotls.lua:2](../lua/lspconfig/configs/dotls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## dprint
https://github.com/dprint/dprint
Pluggable and configurable code formatting platform written in Rust.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.dprint.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dprint", "lsp" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-10-28 11:47:28 +00:00
{ "javascript", "javascriptreact", "typescript", "typescriptreact", "json", "jsonc", "markdown", "python", "toml", "rust", "roslyn", "graphql" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/dprint.lua:4](../lua/lspconfig/configs/dprint.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## drools_lsp
https://github.com/kiegroup/drools-lsp
Language server for the [Drools Rule Language (DRL)](https://docs.drools.org/latest/drools-docs/docs-website/drools/language-reference/#con-drl_drl-rules).
The `drools-lsp` server is a self-contained java jar file (`drools-lsp-server-jar-with-dependencies.jar`), and can be downloaded from [https://github.com/kiegroup/drools-lsp/releases/](https://github.com/kiegroup/drools-lsp/releases/).
Configuration information:
```lua
-- Option 1) Specify the entire command:
require('lspconfig').drools_lsp.setup {
cmd = { '/path/to/java', '-jar', '/path/to/drools-lsp-server-jar-with-dependencies.jar' },
}
-- Option 2) Specify just the jar path (the JAVA_HOME environment variable will be respected if present):
require('lspconfig').drools_lsp.setup {
drools = { jar = '/path/to/drools-lsp-server-jar-with-dependencies.jar' },
}
-- Option 3) Specify the java bin and/or java opts in addition to the jar path:
require('lspconfig').drools_lsp.setup {
drools = {
java = { bin = '/path/to/java', opts = { '-Xmx100m' } },
jar = '/path/to/drools-lsp-server-jar-with-dependencies.jar',
},
}
```
Neovim does not yet have automatic detection for the `drools` filetype, but it can be added with:
```lua
vim.cmd [[ autocmd BufNewFile,BufRead *.drl set filetype=drools ]]
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.drools_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "drools" }
```
docs: update configs.md skip-checks: true
2024-12-21 15:10:48 +00:00
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/drools_lsp.lua:36](../lua/lspconfig/configs/drools_lsp.lua#L36)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/drools_lsp.lua:36](../lua/lspconfig/configs/drools_lsp.lua#L36)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ds_pinyin_lsp
https://github.com/iamcco/ds-pinyin-lsp
Dead simple Pinyin language server for input Chinese without IME(input method).
To install, download the latest [release](https://github.com/iamcco/ds-pinyin-lsp/releases) and ensure `ds-pinyin-lsp` is on your path.
And make ensure the database file `dict.db3` is also downloaded. And put the path to `dict.dbs` in the following code.
```lua
require('lspconfig').ds_pinyin_lsp.setup {
init_options = {
db_path = "your_path_to_database"
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ds_pinyin_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- DsPinyinCompletionOff: Turn off the ds-pinyin-lsp completion
- DsPinyinCompletionOn: Turn on the ds-pinyin-lsp completion
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ds-pinyin-lsp" }
```
- `filetypes` :
```lua
{ "markdown", "org" }
```
- `init_options` :
```lua
{
completion_on = true,
match_as_same_as_input = true,
match_long_input = true,
max_suggest = 15,
show_symbols = true,
show_symbols_by_n_times = 0,
show_symbols_only_follow_by_hanzi = false
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ds_pinyin_lsp.lua:33](../lua/lspconfig/configs/ds_pinyin_lsp.lua#L33)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## earthlyls
https://github.com/glehmann/earthlyls
A fast language server for earthly.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.earthlyls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "earthlyls" }
```
- `filetypes` :
```lua
{ "earthfile" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/earthlyls.lua:4](../lua/lspconfig/configs/earthlyls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ecsact
https://github.com/ecsact-dev/ecsact_lsp_server
Language server for Ecsact.
The default cmd assumes `ecsact_lsp_server` is in your PATH. Typically from the
Ecsact SDK: https://ecsact.dev/start
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ecsact.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ecsact_lsp_server", "--stdio" }
```
- `filetypes` :
```lua
{ "ecsact" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ecsact.lua:4](../lua/lspconfig/configs/ecsact.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## efm
https://github.com/mattn/efm-langserver
General purpose Language Server that can use specified error message format generated from specified command.
Requires at minimum EFM version [v0.0.38](https://github.com/mattn/efm-langserver/releases/tag/v0.0.38) to support
launching the language server on single files. If on an older version of EFM, disable single file support:
```lua
require('lspconfig')['efm'].setup{
settings = ..., -- You must populate this according to the EFM readme
filetypes = ..., -- Populate this according to the note below
single_file_support = false, -- This is the important line for supporting older version of EFM
}
```
Note: In order for neovim's built-in language server client to send the appropriate `languageId` to EFM, **you must
specify `filetypes` in your call to `setup{}`**. Otherwise `lspconfig` will launch EFM on the `BufEnter` instead
of the `FileType` autocommand, and the `filetype` variable used to populate the `languageId` will not yet be set.
```lua
require('lspconfig')['efm'].setup{
settings = ..., -- You must populate this according to the EFM readme
filetypes = { 'python','cpp','lua' }
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.efm.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "efm-langserver" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/efm.lua:2](../lua/lspconfig/configs/efm.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## elixirls
https://github.com/elixir-lsp/elixir-ls
`elixir-ls` can be installed by following the instructions [here](https://github.com/elixir-lsp/elixir-ls#building-and-running).
docs: update configs.md skip-checks: true
2024-12-02 16:27:12 +00:00
1. Download the zip from https://github.com/elixir-lsp/elixir-ls/releases/latest/
2. Unzip it and make it executable.
```bash
unzip elixir-ls.zip -d /path/to/elixir-ls
# Unix
chmod +x /path/to/elixir-ls/language_server.sh
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
**By default, elixir-ls doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set `cmd` to the absolute path ($HOME and ~ are not expanded) of your unzipped elixir-ls.
```lua
require'lspconfig'.elixirls.setup{
-- Unix
cmd = { "/path/to/elixir-ls/language_server.sh" };
-- Windows
cmd = { "/path/to/elixir-ls/language_server.bat" };
...
}
```
'root_dir' is chosen like this: if two or more directories containing `mix.exs` were found when searching directories upward, the second one (higher up) is chosen, with the assumption that it is the root of an umbrella app. Otherwise the directory containing the single mix.exs that was found is chosen.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.elixirls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "elixir", "eelixir", "heex", "surface" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/elixirls.lua:2](../lua/lspconfig/configs/elixirls.lua#L2)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## elmls
https://github.com/elm-tooling/elm-language-server#installation
If you don't want to use Nvim to install it, then you can use:
```sh
npm install -g elm elm-test elm-format @elm-tooling/elm-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.elmls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
offsetEncoding = { "utf-8", "utf-16" }
}
```
- `cmd` :
```lua
{ "elm-language-server" }
```
- `filetypes` :
```lua
{ "elm" }
```
- `init_options` :
```lua
{
disableElmLSDiagnostics = false,
elmReviewDiagnostics = "off",
onlyUpdateDiagnosticsOnSave = false,
skipInstallPackageConfirmation = false
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/elmls.lua:7](../lua/lspconfig/configs/elmls.lua#L7)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## elp
https://whatsapp.github.io/erlang-language-platform
ELP integrates Erlang into modern IDEs via the language server protocol and was
inspired by rust-analyzer.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.elp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "elp", "server" }
```
- `filetypes` :
```lua
{ "erlang" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/elp.lua:4](../lua/lspconfig/configs/elp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ember
https://github.com/ember-tooling/ember-language-server
`ember-language-server` can be installed via `npm`:
```sh
npm install -g @ember-tooling/ember-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ember.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ember-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "handlebars", "typescript", "javascript", "typescript.glimmer", "javascript.glimmer" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ember.lua:4](../lua/lspconfig/configs/ember.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## emmet_language_server
https://github.com/olrtg/emmet-language-server
Package can be installed via `npm`:
```sh
npm install -g @olrtg/emmet-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.emmet_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "emmet-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "css", "eruby", "html", "htmldjango", "javascriptreact", "less", "pug", "sass", "scss", "typescriptreact", "htmlangular" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/emmet_language_server.lua:2](../lua/lspconfig/configs/emmet_language_server.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## emmet_ls
https://github.com/aca/emmet-ls
Package can be installed via `npm`:
```sh
npm install -g emmet-ls
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.emmet_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "emmet-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "astro", "css", "eruby", "html", "htmldjango", "javascriptreact", "less", "pug", "sass", "scss", "svelte", "typescriptreact", "vue", "htmlangular" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/emmet_ls.lua:2](../lua/lspconfig/configs/emmet_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## erg_language_server
https://github.com/erg-lang/erg#flags ELS
ELS (erg-language-server) is a language server for the Erg programming language.
erg-language-server can be installed via `cargo` and used as follows:
```sh
cargo install erg --features els
erg --language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.erg_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "erg", "--language-server" }
```
- `filetypes` :
```lua
{ "erg" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/erg_language_server.lua:4](../lua/lspconfig/configs/erg_language_server.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## erlangls
https://erlang-ls.github.io
Language Server for Erlang.
Clone [erlang_ls](https://github.com/erlang-ls/erlang_ls)
Compile the project with `make` and copy resulting binaries somewhere in your $PATH eg. `cp _build/*/bin/* ~/local/bin`
Installation instruction can be found [here](https://github.com/erlang-ls/erlang_ls).
Installation requirements:
- [Erlang OTP 21+](https://github.com/erlang/otp)
- [rebar3 3.9.1+](https://github.com/erlang/rebar3)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.erlangls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "erlang_ls" }
```
- `filetypes` :
```lua
{ "erlang" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/erlangls.lua:4](../lua/lspconfig/configs/erlangls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## esbonio
https://github.com/swyddfa/esbonio
Esbonio is a language server for [Sphinx](https://www.sphinx-doc.org/en/master/) documentation projects.
The language server can be installed via pip
```
pip install esbonio
```
Since Sphinx is highly extensible you will get best results if you install the language server in the same
Python environment as the one used to build your documentation. To ensure that the correct Python environment
is picked up, you can either launch `nvim` with the correct environment activated.
```
source env/bin/activate
nvim
```
Or you can modify the default `cmd` to include the full path to the Python interpreter.
```lua
require'lspconfig'.esbonio.setup {
cmd = { '/path/to/virtualenv/bin/python', '-m', 'esbonio' }
}
```
Esbonio supports a number of config values passed as `init_options` on startup, for example.
```lua
require'lspconfig'.esbonio.setup {
init_options = {
server = {
logLevel = "debug"
},
sphinx = {
confDir = "/path/to/docs",
srcDir = "${confDir}/../docs-src"
}
}
```
A full list and explanation of the available options can be found [here](https://docs.esbon.io/en/esbonio-language-server-v0.16.4/lsp/getting-started.html?editor=neovim-lspconfig#configuration)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.esbonio.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "python3", "-m", "esbonio" }
```
- `filetypes` :
```lua
{ "rst" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/esbonio.lua:2](../lua/lspconfig/configs/esbonio.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## eslint
https://github.com/hrsh7th/vscode-langservers-extracted
`vscode-eslint-language-server` is a linting engine for JavaScript / Typescript.
It can be installed via `npm`:
```sh
npm i -g vscode-langservers-extracted
```
`vscode-eslint-language-server` provides an `EslintFixAll` command that can be used to format a document on save:
```lua
lspconfig.eslint.setup({
--- ...
on_attach = function(client, bufnr)
vim.api.nvim_create_autocmd("BufWritePre", {
buffer = bufnr,
command = "EslintFixAll",
})
end,
})
```
See [vscode-eslint](https://github.com/microsoft/vscode-eslint/blob/55871979d7af184bf09af491b6ea35ebd56822cf/server/src/eslintServer.ts#L216-L229) for configuration options.
Messages handled in lspconfig: `eslint/openDoc`, `eslint/confirmESLintExecution`, `eslint/probeFailed`, `eslint/noLibrary`
Additional messages you can handle: `eslint/noConfig`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.eslint.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- EslintFixAll: Fix all eslint problems for this buffer
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscode-eslint-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx", "vue", "svelte", "astro" }
```
- `handlers` :
```lua
{
["eslint/confirmESLintExecution"] = <function 1>,
["eslint/noLibrary"] = <function 2>,
["eslint/openDoc"] = <function 3>,
["eslint/probeFailed"] = <function 4>
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/eslint.lua:51](../lua/lspconfig/configs/eslint.lua#L51)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/eslint.lua:51](../lua/lspconfig/configs/eslint.lua#L51)
- `settings` :
```lua
{
codeAction = {
disableRuleComment = {
enable = true,
location = "separateLine"
regen docs
2024-10-24 15:06:10 +00:00
},
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
showDocumentation = {
enable = true
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
},
codeActionOnSave = {
enable = false,
mode = "all"
},
experimental = {
useFlatConfig = false
},
format = true,
nodePath = "",
onIgnoredFiles = "off",
problems = {
shortenToSingleLine = false
},
quiet = false,
rulesCustomizations = {},
run = "onType",
useESLintClass = false,
validate = "on",
workingDirectory = {
mode = "location"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## facility_language_server
https://github.com/FacilityApi/FacilityLanguageServer
Facility language server protocol (LSP) support.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.facility_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "facility-language-server" }
```
- `filetypes` :
```lua
{ "fsd" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/facility_language_server.lua:2](../lua/lspconfig/configs/facility_language_server.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fennel_language_server
https://github.com/rydesun/fennel-language-server
Fennel language server protocol (LSP) support.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fennel_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "fennel-language-server" }
```
- `filetypes` :
```lua
{ "fennel" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fennel_language_server.lua:2](../lua/lspconfig/configs/fennel_language_server.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fennel_ls
https://sr.ht/~xerool/fennel-ls/
A language server for fennel.
docs: update configs.md skip-checks: true
2024-10-06 00:58:09 +00:00
fennel-ls is configured using the closest file to your working directory named `flsproject.fnl`.
All fennel-ls configuration options [can be found here](https://git.sr.ht/~xerool/fennel-ls/tree/HEAD/docs/manual.md#configuration).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fennel_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
offsetEncoding = { "utf-8", "utf-16" }
}
```
- `cmd` :
```lua
{ "fennel-ls" }
```
- `filetypes` :
```lua
{ "fennel" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fennel_ls.lua:4](../lua/lspconfig/configs/fennel_ls.lua#L4)
- `settings` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-01 22:12:54 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fish_lsp
https://github.com/ndonfris/fish-lsp
A Language Server Protocol (LSP) tailored for the fish shell.
This project aims to enhance the coding experience for fish,
by introducing a suite of intelligent features like auto-completion,
scope aware symbol analysis, per-token hover generation, and many others.
[homepage](https://www.fish-lsp.dev/)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fish_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "fish-lsp", "start" }
```
- `cmd_env` :
```lua
{
fish_lsp_show_client_popups = false
}
```
- `filetypes` :
```lua
{ "fish" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fish_lsp.lua:2](../lua/lspconfig/configs/fish_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## flow
https://flow.org/
https://github.com/facebook/flow
See below for how to setup Flow itself.
https://flow.org/en/docs/install/
See below for lsp command options.
```sh
npx flow lsp --help
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.flow.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "npx", "--no-install", "flow", "lsp" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/flow.lua:4](../lua/lspconfig/configs/flow.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## flux_lsp
https://github.com/influxdata/flux-lsp
`flux-lsp` can be installed via `cargo`:
```sh
cargo install --git https://github.com/influxdata/flux-lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.flux_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "flux-lsp" }
```
- `filetypes` :
```lua
{ "flux" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/flux_lsp.lua:2](../lua/lspconfig/configs/flux_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## foam_ls
https://github.com/FoamScience/foam-language-server
`foam-language-server` can be installed via `npm`
```sh
npm install -g foam-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.foam_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "foam-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "foam", "OpenFOAM" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/foam_ls.lua:4](../lua/lspconfig/configs/foam_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fortls
https://fortls.fortran-lang.org/index.html
fortls is a Fortran Language Server, the server can be installed via pip
```sh
pip install fortls
```
Settings to the server can be passed either through the `cmd` option or through
a local configuration file e.g. `.fortls`. For more information
see the `fortls` [documentation](https://fortls.fortran-lang.org/options.html).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fortls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "fortls", "--notify_init", "--hover_signature", "--hover_language=fortran", "--use_signature_help" }
```
- `filetypes` :
```lua
{ "fortran" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fortls.lua:4](../lua/lspconfig/configs/fortls.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fsautocomplete
https://github.com/fsharp/FsAutoComplete
Language Server for F# provided by FsAutoComplete (FSAC).
FsAutoComplete requires the [dotnet-sdk](https://dotnet.microsoft.com/download) to be installed.
The preferred way to install FsAutoComplete is with `dotnet tool install --global fsautocomplete`.
Instructions to compile from source are found on the main [repository](https://github.com/fsharp/FsAutoComplete).
You may also need to configure the filetype as Vim defaults to Forth for `*.fs` files:
`autocmd BufNewFile,BufRead *.fs,*.fsx,*.fsi set filetype=fsharp`
This is automatically done by plugins such as [PhilT/vim-fsharp](https://github.com/PhilT/vim-fsharp), [fsharp/vim-fsharp](https://github.com/fsharp/vim-fsharp), and [adelarsq/neofsharp.vim](https://github.com/adelarsq/neofsharp.vim).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fsautocomplete.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "fsautocomplete", "--adaptive-lsp-server-enabled" }
```
- `filetypes` :
```lua
{ "fsharp" }
```
- `init_options` :
```lua
{
AutomaticWorkspaceInit = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fsautocomplete.lua:4](../lua/lspconfig/configs/fsautocomplete.lua#L4)
- `settings` :
```lua
{
FSharp = {
EnableReferenceCodeLens = true,
ExternalAutocomplete = false,
InterfaceStubGeneration = true,
InterfaceStubGenerationMethodBody = 'failwith "Not Implemented"',
InterfaceStubGenerationObjectIdentifier = "this",
Linter = true,
RecordStubGeneration = true,
RecordStubGenerationBody = 'failwith "Not Implemented"',
ResolveNamespaces = true,
SimplifyNameAnalyzer = true,
UnionCaseStubGeneration = true,
UnionCaseStubGenerationBody = 'failwith "Not Implemented"',
UnusedDeclarationsAnalyzer = true,
UnusedOpensAnalyzer = true,
UseSdkScripts = true,
keywordsAutocomplete = true
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fsharp_language_server
F# Language Server
https://github.com/faldor20/fsharp-language-server
An implementation of the language server protocol using the F# Compiler Service.
Build the project from source and override the command path to location of DLL.
If filetype determination is not already performed by an available plugin ([PhilT/vim-fsharp](https://github.com/PhilT/vim-fsharp), [fsharp/vim-fsharp](https://github.com/fsharp/vim-fsharp), and [adelarsq/neofsharp.vim](https://github.com/adelarsq/neofsharp.vim).
), then the following must be added to initialization configuration:
`autocmd BufNewFile,BufRead *.fs,*.fsx,*.fsi set filetype=fsharp`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fsharp_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dotnet", "FSharpLanguageServer.dll" }
```
- `filetypes` :
```lua
{ "fsharp" }
```
- `init_options` :
```lua
{
AutomaticWorkspaceInit = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fsharp_language_server.lua:4](../lua/lspconfig/configs/fsharp_language_server.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## fstar
https://github.com/FStarLang/FStar
LSP support is included in FStar. Make sure `fstar.exe` is in your PATH.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.fstar.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "fstar.exe", "--lsp" }
```
- `filetypes` :
```lua
{ "fstar" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/fstar.lua:2](../lua/lspconfig/configs/fstar.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## futhark_lsp
https://github.com/diku-dk/futhark
Futhark Language Server
This language server comes with the futhark compiler and is run with the command
```
futhark lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.futhark_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "futhark", "lsp" }
```
- `filetypes` :
```lua
{ "futhark", "fut" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/futhark_lsp.lua:2](../lua/lspconfig/configs/futhark_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gdscript
https://github.com/godotengine/godot
Language server for GDScript, used by Godot Engine.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gdscript.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
docs: update configs.md skip-checks: true
2024-12-08 17:39:00 +00:00
- `cmd` source (use "gF" to visit): [../lua/lspconfig/configs/gdscript.lua:7](../lua/lspconfig/configs/gdscript.lua#L7)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `filetypes` :
```lua
{ "gd", "gdscript", "gdscript3" }
```
docs: update configs.md skip-checks: true
2024-12-08 17:39:00 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gdscript.lua:7](../lua/lspconfig/configs/gdscript.lua#L7)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gdshader_lsp
https://github.com/godofavacyn/gdshader-lsp
A language server for the Godot Shading language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gdshader_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "gdshader-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "gdshader", "gdshaderinc" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gdshader_lsp.lua:4](../lua/lspconfig/configs/gdshader_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2025-01-13 08:40:59 +00:00
## gh_actions_ls
https://github.com/lttb/gh-actions-language-server
Language server for GitHub Actions.
`gh-actions-language-server` can be installed via `npm`:
```sh
npm install -g gh-actions-language-server
```
Snippet to enable the language server:
```lua
require'lspconfig'.gh_actions_ls.setup{}
```
Default config:
- `capabilities` :
```lua
{
workspace = {
didChangeWorkspaceFolders = {
dynamicRegistration = true
}
}
}
```
- `cmd` :
```lua
{ "gh-actions-language-server", "--stdio" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2025-01-13 14:22:42 +00:00
{ "yaml" }
docs: update configs.md skip-checks: true
2025-01-13 08:40:59 +00:00
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gh_actions_ls.lua:4](../lua/lspconfig/configs/gh_actions_ls.lua#L4)
docs: update configs.md skip-checks: true
2025-01-13 14:22:42 +00:00
- `single_file_support` : `false`
docs: update configs.md skip-checks: true
2025-01-13 08:40:59 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ghcide
https://github.com/digital-asset/ghcide
A library for building Haskell IDE tooling.
"ghcide" isn't for end users now. Use "haskell-language-server" instead of "ghcide".
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ghcide.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ghcide", "--lsp" }
```
- `filetypes` :
```lua
{ "haskell", "lhaskell" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ghcide.lua:4](../lua/lspconfig/configs/ghcide.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ghdl_ls
https://github.com/ghdl/ghdl-language-server
A language server for VHDL, using ghdl as its backend.
`ghdl-ls` is part of pyghdl, for installation instructions see
[the upstream README](https://github.com/ghdl/ghdl/tree/master/pyGHDL/lsp).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ghdl_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ghdl-ls" }
```
- `filetypes` :
```lua
{ "vhdl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ghdl_ls.lua:4](../lua/lspconfig/configs/ghdl_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ginko_ls
`ginko_ls` is meant to be a feature-complete language server for device-trees.
Language servers can be used in many editors, such as Visual Studio Code, Emacs
or Vim
Install `ginko_ls` from https://github.com/Schottkyc137/ginko and add it to path
`ginko_ls` doesn't require any configuration.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ginko_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ginko_ls" }
```
- `filetypes` :
```lua
{ "dts" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ginko_ls.lua:2](../lua/lspconfig/configs/ginko_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gitlab_ci_ls
https://github.com/alesbrelih/gitlab-ci-ls
Language Server for Gitlab CI
`gitlab-ci-ls` can be installed via cargo:
cargo install gitlab-ci-ls
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gitlab_ci_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "gitlab-ci-ls" }
```
- `filetypes` :
```lua
{ "yaml.gitlab" }
```
- `init_options` :
```lua
{
cache_path = "/home/user/.cache/gitlab-ci-ls/",
log_path = "/home/user/.cache/gitlab-ci-ls//log/gitlab-ci-ls.log"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gitlab_ci_ls.lua:5](../lua/lspconfig/configs/gitlab_ci_ls.lua#L5)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## glasgow
https://github.com/nolanderc/glasgow
Provides language features for WGSL (WebGPU Shading Language):
- Completions:
- Local functions/variables/types.
- Fields and swizzles.
- Builtin types and functions (`dot`, `reflect`, `textureSample`, `vec3`, `mat4x2`, etc.)
- Hover Documentation:
- Function signatures.
- Variable types.
- Includes builtin types and functions. Text is taken from the WGSL specification.
- Goto Definition
- Find all References
- Rename
- Formatter
`glasgow` can be installed via `cargo`:
```sh
cargo install glasgow
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.glasgow.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "glasgow" }
```
- `filetypes` :
```lua
{ "wgsl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/glasgow.lua:2](../lua/lspconfig/configs/glasgow.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gleam
https://github.com/gleam-lang/gleam
A language server for Gleam Programming Language.
[Installation](https://gleam.run/getting-started/installing/)
It can be i
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gleam.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "gleam", "lsp" }
```
- `filetypes` :
```lua
{ "gleam" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gleam.lua:4](../lua/lspconfig/configs/gleam.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## glint
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/typed-ember/glint
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
https://typed-ember.gitbook.io/glint/
`glint-language-server` is installed when adding `@glint/core` to your project's devDependencies:
```sh
npm install @glint/core --save-dev
```
or
```sh
yarn add -D @glint/core
```
or
```sh
pnpm add -D @glint/core
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.glint.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "glint-language-server" }
```
- `filetypes` :
```lua
{ "html.handlebars", "handlebars", "typescript", "typescript.glimmer", "javascript", "javascript.glimmer" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/glint.lua:4](../lua/lspconfig/configs/glint.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/glint.lua:4](../lua/lspconfig/configs/glint.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## glsl_analyzer
https://github.com/nolanderc/glsl_analyzer
Language server for GLSL
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
regen docs
2024-10-24 15:06:10 +00:00
require'lspconfig'.glsl_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{}
```
- `cmd` :
```lua
{ "glsl_analyzer" }
```
- `filetypes` :
```lua
{ "glsl", "vert", "tesc", "tese", "frag", "geom", "comp" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/glsl_analyzer.lua:2](../lua/lspconfig/configs/glsl_analyzer.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## glslls
https://github.com/svenstaro/glsl-language-server
Language server implementation for GLSL
`glslls` can be compiled and installed manually, or, if your distribution has access to the AUR,
via the `glsl-language-server` AUR package
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.glslls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
offsetEncoding = { "utf-8", "utf-16" },
textDocument = {
completion = {
editsNearCursor = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "glslls", "--stdin" }
```
- `filetypes` :
```lua
{ "glsl", "vert", "tesc", "tese", "frag", "geom", "comp" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/glslls.lua:2](../lua/lspconfig/configs/glslls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## golangci_lint_ls
Combination of both lint server and client
https://github.com/nametake/golangci-lint-langserver
https://github.com/golangci/golangci-lint
Installation of binaries needed is done via
```
go install github.com/nametake/golangci-lint-langserver@latest
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.golangci_lint_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "golangci-lint-langserver" }
```
- `filetypes` :
```lua
{ "go", "gomod" }
```
- `init_options` :
```lua
{
command = { "golangci-lint", "run", "--out-format", "json" }
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/golangci_lint_ls.lua:4](../lua/lspconfig/configs/golangci_lint_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gopls
https://github.com/golang/tools/tree/master/gopls
Google's lsp server for golang.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gopls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "gopls" }
```
- `filetypes` :
```lua
{ "go", "gomod", "gowork", "gotmpl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gopls.lua:6](../lua/lspconfig/configs/gopls.lua#L6)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## gradle_ls
https://github.com/microsoft/vscode-gradle
Microsoft's lsp server for gradle files
If you're setting this up manually, build vscode-gradle using `./gradlew installDist` and point `cmd` to the `gradle-language-server` generated in the build directory
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.gradle_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "gradle-language-server" }
```
- `filetypes` :
```lua
{ "groovy" }
```
- `init_options` :
```lua
{
settings = {
gradleWrapperEnabled = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/gradle_ls.lua:9](../lua/lspconfig/configs/gradle_ls.lua#L9)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## grammarly
https://github.com/znck/grammarly
`grammarly-languageserver` can be installed via `npm`:
```sh
npm i -g grammarly-languageserver
```
WARNING: Since this language server uses Grammarly's API, any document you open with it running is shared with them. Please evaluate their [privacy policy](https://www.grammarly.com/privacy-policy) before using this.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.grammarly.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "grammarly-languageserver", "--stdio" }
```
- `filetypes` :
```lua
{ "markdown" }
```
- `handlers` :
```lua
{
["$/updateDocumentState"] = <function 1>
}
```
- `init_options` :
```lua
{
clientId = "client_BaDkMgx4X19X9UxxYRCXZo"
}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/grammarly.lua:2](../lua/lspconfig/configs/grammarly.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## graphql
https://github.com/graphql/graphiql/tree/main/packages/graphql-language-service-cli
`graphql-lsp` can be installed via `npm`:
```sh
npm install -g graphql-language-service-cli
```
Note that you must also have [the graphql package](https://github.com/graphql/graphql-js) installed within your project and create a [GraphQL config file](https://the-guild.dev/graphql/config/docs).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.graphql.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "graphql-lsp", "server", "-m", "stream" }
```
- `filetypes` :
```lua
{ "graphql", "typescriptreact", "javascriptreact" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/graphql.lua:4](../lua/lspconfig/configs/graphql.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## groovyls
https://github.com/prominic/groovy-language-server.git
Requirements:
- Linux/macOS (for now)
- Java 11+
`groovyls` can be installed by following the instructions [here](https://github.com/prominic/groovy-language-server.git#build).
If you have installed groovy language server, you can set the `cmd` custom path as follow:
```lua
require'lspconfig'.groovyls.setup{
-- Unix
cmd = { "java", "-jar", "path/to/groovyls/groovy-language-server-all.jar" },
...
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.groovyls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "java", "-jar", "groovy-language-server-all.jar" }
```
- `filetypes` :
```lua
{ "groovy" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/groovyls.lua:4](../lua/lspconfig/configs/groovyls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## guile_ls
https://codeberg.org/rgherdt/scheme-lsp-server
The recommended way is to install guile-lsp-server is using Guix. Unfortunately it is still not available at the official Guix channels, but you can use the provided channel guix.scm in the repo:
```sh
guix package -f guix.scm
```
Checkout the repo for more info.
Note: This LSP will start on `scheme.guile` filetype. You can set this file type using `:help modeline` or adding https://gitlab.com/HiPhish/guile.vim to your plugins to automatically set it.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.guile_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "guile-lsp-server" }
```
- `filetypes` :
```lua
{ "scheme.guile" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/guile_ls.lua:3](../lua/lspconfig/configs/guile_ls.lua#L3)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## harper_ls
docs(harper_ls): fix links to current harper repo (#3444)
2024-11-22 09:40:24 +00:00
https://github.com/elijah-potter/harper
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
The language server for Harper, the slim, clean language checker for developers.
docs(harper_ls): fix links to current harper repo (#3444)
2024-11-22 09:40:24 +00:00
See [docs](https://github.com/elijah-potter/harper/blob/master/harper-ls/README.md#configuration) for more information on settings.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
In short, however, they should look something like this:
```lua
lspconfig.harper_ls.setup {
settings = {
["harper-ls"] = {
userDictPath = "~/dict.txt"
}
},
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.harper_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "harper-ls", "--stdio" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2025-01-04 12:54:27 +00:00
{ "c", "cpp", "cs", "gitcommit", "go", "html", "java", "javascript", "lua", "markdown", "nix", "python", "ruby", "rust", "swift", "toml", "typescript", "typescriptreact", "haskell", "cmake" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/harper_ls.lua:2](../lua/lspconfig/configs/harper_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## haxe_language_server
https://github.com/vshaxe/haxe-language-server
The Haxe language server can be built by running the following commands from
the project's root directory:
npm install
npx lix run vshaxe-build -t language-server
This will create `bin/server.js`. Note that the server requires Haxe 3.4.0 or
higher.
After building the language server, set the `cmd` setting in your setup
function:
```lua
lspconfig.haxe_language_server.setup({
cmd = {"node", "path/to/bin/server.js"},
})
```
By default, the language server is configured with the HXML compiler arguments
contained in the first `.hxml` file found in your project's root directory.
If you want to specify which one to use, set the `init_options.displayArguments`
setting:
```lua
lspconfig.haxe_language_server.setup({
-- ...
init_options = {
displayArguments = { "build.hxml" },
},
})
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.haxe_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "haxe-language-server" }
```
- `filetypes` :
```lua
{ "haxe" }
```
- `init_options` :
```lua
{}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/haxe_language_server.lua:10](../lua/lspconfig/configs/haxe_language_server.lua#L10)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/haxe_language_server.lua:10](../lua/lspconfig/configs/haxe_language_server.lua#L10)
- `settings` :
```lua
{
haxe = {
executable = "haxe"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hdl_checker
https://github.com/suoto/hdl_checker
Language server for hdl-checker.
Install using: `pip install hdl-checker --upgrade`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hdl_checker.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hdl_checker", "--lsp" }
```
- `filetypes` :
```lua
{ "vhdl", "verilog", "systemverilog" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hdl_checker.lua:2](../lua/lspconfig/configs/hdl_checker.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## helm_ls
https://github.com/mrjosh/helm-ls
Helm Language server. (This LSP is in early development)
`helm Language server` can be installed by following the instructions [here](https://github.com/mrjosh/helm-ls).
The default `cmd` assumes that the `helm_ls` binary can be found in `$PATH`.
If need Helm file highlight use [vim-helm](https://github.com/towolf/vim-helm) plugin.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.helm_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
workspace = {
didChangeWatchedFiles = {
dynamicRegistration = true
regen docs
2024-10-24 15:06:10 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "helm_ls", "serve" }
```
- `filetypes` :
```lua
{ "helm" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/helm_ls.lua:4](../lua/lspconfig/configs/helm_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hhvm
Language server for programs written in Hack
https://hhvm.com/
https://github.com/facebook/hhvm
See below for how to setup HHVM & typechecker:
https://docs.hhvm.com/hhvm/getting-started/getting-started
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hhvm.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hh_client", "lsp" }
```
- `filetypes` :
```lua
{ "php", "hack" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hhvm.lua:4](../lua/lspconfig/configs/hhvm.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hie
https://github.com/haskell/haskell-ide-engine
the following init_options are supported (see https://github.com/haskell/haskell-ide-engine#configuration):
```lua
init_options = {
languageServerHaskell = {
hlintOn = bool;
maxNumberOfProblems = number;
diagnosticsDebounceDuration = number;
liquidOn = bool (default false);
completionSnippetsOn = bool (default true);
formatOnImportOn = bool (default true);
formattingProvider = string (default "brittany", alternate "floskell");
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hie.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hie-wrapper", "--lsp" }
```
- `filetypes` :
```lua
{ "haskell" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hie.lua:4](../lua/lspconfig/configs/hie.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hlasm
regen docs
2024-10-24 15:06:10 +00:00
`hlasm_language_server` is a language server for the High Level Assembler language used on IBM SystemZ mainframes.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
To learn how to configure the HLASM language server, see the [HLASM Language Support documentation](https://github.com/eclipse-che4z/che-che4z-lsp-for-hlasm).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hlasm.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hlasm_language_server" }
```
- `filetypes` :
```lua
{ "hlasm" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hlasm.lua:4](../lua/lspconfig/configs/hlasm.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hls
https://github.com/haskell/haskell-language-server
Haskell Language Server
If you are using HLS 1.9.0.0, enable the language server to launch on Cabal files as well:
```lua
require('lspconfig')['hls'].setup{
filetypes = { 'haskell', 'lhaskell', 'cabal' },
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "haskell-language-server-wrapper", "--lsp" }
```
- `filetypes` :
```lua
{ "haskell", "lhaskell" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hls.lua:4](../lua/lspconfig/configs/hls.lua#L4)
- `settings` :
```lua
{
haskell = {
cabalFormattingProvider = "cabalfmt",
formattingProvider = "ormolu"
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hoon_ls
https://github.com/urbit/hoon-language-server
A language server for Hoon.
The language server can be installed via `npm install -g @hoon-language-server`
Start a fake ~zod with `urbit -F zod`.
Start the language server at the Urbit Dojo prompt with: `|start %language-server`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hoon_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hoon-language-server" }
```
- `filetypes` :
```lua
{ "hoon" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hoon_ls.lua:2](../lua/lspconfig/configs/hoon_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## html
https://github.com/hrsh7th/vscode-langservers-extracted
`vscode-html-language-server` can be installed via `npm`:
```sh
npm i -g vscode-langservers-extracted
```
Neovim does not currently include built-in snippets. `vscode-html-language-server` only provides completions when snippet support is enabled.
To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.
The code-formatting feature of the lsp can be controlled with the `provideFormatter` option.
```lua
--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true
require'lspconfig'.html.setup {
capabilities = capabilities,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.html.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscode-html-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "html", "templ" }
```
- `init_options` :
```lua
{
configurationSection = { "html", "css", "javascript" },
embeddedLanguages = {
css = true,
javascript = true
},
provideFormatter = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/html.lua:4](../lua/lspconfig/configs/html.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## htmx
https://github.com/ThePrimeagen/htmx-lsp
`htmx-lsp` can be installed via `cargo`:
```sh
cargo install htmx-lsp
```
Lsp is still very much work in progress and experimental. Use at your own risk.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.htmx.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "htmx-lsp" }
```
- `filetypes` :
```lua
{ "aspnetcorerazor", "astro", "astro-markdown", "blade", "clojure", "django-html", "htmldjango", "edge", "eelixir", "elixir", "ejs", "erb", "eruby", "gohtml", "gohtmltmpl", "haml", "handlebars", "hbs", "html", "htmlangular", "html-eex", "heex", "jade", "leaf", "liquid", "markdown", "mdx", "mustache", "njk", "nunjucks", "php", "razor", "slim", "twig", "javascript", "javascriptreact", "reason", "rescript", "typescript", "typescriptreact", "vue", "svelte", "templ" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/htmx.lua:2](../lua/lspconfig/configs/htmx.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hydra_lsp
https://github.com/Retsediv/hydra-lsp
LSP for Hydra Python package config files.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hydra_lsp.setup{}
regen docs
2024-10-24 15:06:10 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hydra-lsp" }
```
- `filetypes` :
```lua
{ "yaml" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hydra_lsp.lua:4](../lua/lspconfig/configs/hydra_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## hyprls
https://github.com/hyprland-community/hyprls
`hyprls` can be installed via `go`:
```sh
go install github.com/ewen-lbh/hyprls/cmd/hyprls@latest
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.hyprls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "hyprls", "--stdio" }
```
- `filetypes` :
```lua
{ "hyprlang" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/hyprls.lua:2](../lua/lspconfig/configs/hyprls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## idris2_lsp
https://github.com/idris-community/idris2-lsp
The Idris 2 language server.
Plugins for the Idris 2 filetype include
[Idris2-Vim](https://github.com/edwinb/idris2-vim) (fewer features, stable) and
[Nvim-Idris2](https://github.com/ShinKage/nvim-idris2) (cutting-edge,
experimental).
Idris2-Lsp requires a build of Idris 2 that includes the "Idris 2 API" package.
Package managers with known support for this build include the
[AUR](https://aur.archlinux.org/packages/idris2/) and
[Homebrew](https://formulae.brew.sh/formula/idris2#default).
If your package manager does not support the Idris 2 API, you will need to build
Idris 2 from source. Refer to the
[the Idris 2 installation instructions](https://github.com/idris-lang/Idris2/blob/main/INSTALL.md)
for details. Steps 5 and 8 are listed as "optional" in that guide, but they are
necessary in order to make the Idris 2 API available.
You need to install a version of Idris2-Lsp that is compatible with your
version of Idris 2. There should be a branch corresponding to every released
Idris 2 version after v0.4.0. Use the latest commit on that branch. For example,
if you have Idris v0.5.1, you should use the v0.5.1 branch of Idris2-Lsp.
If your Idris 2 version is newer than the newest Idris2-Lsp branch, use the
latest commit on the `master` branch, and set a reminder to check the Idris2-Lsp
repo for the release of a compatible versioned branch.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.idris2_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "idris2-lsp" }
```
- `filetypes` :
```lua
{ "idris2" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/idris2_lsp.lua:4](../lua/lspconfig/configs/idris2_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## intelephense
https://intelephense.com/
`intelephense` can be installed via `npm`:
```sh
npm install -g intelephense
```
docs: update configs.md skip-checks: true
2024-10-24 16:36:34 +00:00
```lua
-- See https://github.com/bmewburn/intelephense-docs/blob/master/installation.md#initialisation-options
init_options = {
storagePath = …, -- Optional absolute path to storage dir. Defaults to os.tmpdir().
globalStoragePath = …, -- Optional absolute path to a global storage dir. Defaults to os.homedir().
licenceKey = …, -- Optional licence key or absolute path to a text file containing the licence key.
clearCache = …, -- Optional flag to clear server state. State can also be cleared by deleting {storagePath}/intelephense
}
-- See https://github.com/bmewburn/intelephense-docs
settings = {
intelephense = {
files = {
maxSize = 1000000;
};
};
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.intelephense.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "intelephense", "--stdio" }
```
- `filetypes` :
```lua
{ "php" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/intelephense.lua:4](../lua/lspconfig/configs/intelephense.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## janet_lsp
https://github.com/CFiggers/janet-lsp
A Language Server Protocol implementation for Janet.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.janet_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "janet-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "janet" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/janet_lsp.lua:4](../lua/lspconfig/configs/janet_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## java_language_server
https://github.com/georgewfraser/java-language-server
Java language server
Point `cmd` to `lang_server_linux.sh` or the equivalent script for macOS/Windows provided by java-language-server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
require'lspconfig'.java_language_server.setup{}
```
Default config:
- `filetypes` :
```lua
{ "java" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/java_language_server.lua:4](../lua/lspconfig/configs/java_language_server.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jdtls
https://projects.eclipse.org/projects/eclipse.jdt.ls
Language server for Java.
IMPORTANT: If you want all the features jdtls has to offer, [nvim-jdtls](https://github.com/mfussenegger/nvim-jdtls)
is highly recommended. If all you need is diagnostics, completion, imports, gotos and formatting and some code actions
you can keep reading here.
For manual installation you can download precompiled binaries from the
[official downloads site](http://download.eclipse.org/jdtls/snapshots/?d)
and ensure that the `PATH` variable contains the `bin` directory of the extracted archive.
```lua
-- init.lua
require'lspconfig'.jdtls.setup{}
```
You can also pass extra custom jvm arguments with the JDTLS_JVM_ARGS environment variable as a space separated list of arguments,
that will be converted to multiple --jvm-arg=<param> args when passed to the jdtls script. This will allow for example tweaking
the jvm arguments or integration with external tools like lombok:
```sh
export JDTLS_JVM_ARGS="-javaagent:$HOME/.local/share/java/lombok.jar"
```
For automatic installation you can use the following unofficial installers/launchers under your own risk:
- [jdtls-launcher](https://github.com/eruizc-dev/jdtls-launcher) (Includes lombok support by default)
```lua
-- init.lua
require'lspconfig'.jdtls.setup{ cmd = { 'jdtls' } }
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jdtls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "jdtls", "-configuration", "/home/user/.cache/jdtls/config", "-data", "/home/user/.cache/jdtls/workspace" }
```
- `filetypes` :
```lua
{ "java" }
```
- `handlers` :
```lua
{
["language/status"] = <function 1>,
["textDocument/codeAction"] = <function 2>,
["textDocument/rename"] = <function 3>,
["workspace/applyEdit"] = <function 4>
}
```
- `init_options` :
```lua
{
jvm_args = {},
workspace = "/home/user/.cache/jdtls/workspace"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jdtls.lua:80](../lua/lspconfig/configs/jdtls.lua#L80)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jedi_language_server
https://github.com/pappasam/jedi-language-server
`jedi-language-server`, a language server for Python, built on top of jedi
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jedi_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "jedi-language-server" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jedi_language_server.lua:13](../lua/lspconfig/configs/jedi_language_server.lua#L13)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jinja_lsp
jinja-lsp enhances minijinja development experience by providing Helix/Nvim users with advanced features such as autocomplete, syntax highlighting, hover, goto definition, code actions and linting.
The file types are not detected automatically, you can register them manually (see below) or override the filetypes:
```lua
vim.filetype.add {
extension = {
jinja = 'jinja',
jinja2 = 'jinja',
j2 = 'jinja',
},
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jinja_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "jinja-lsp" }
```
- `filetypes` :
```lua
{ "jinja" }
```
- `name` :
```lua
"jinja_lsp"
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jinja_lsp.lua:2](../lua/lspconfig/configs/jinja_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jqls
https://github.com/wader/jq-lsp
Language server for jq, written using Go.
You can install the server easily using go install:
```sh
# install directly
go install github.com/wader/jq-lsp@master
# copy binary to $PATH
cp $(go env GOPATH)/bin/jq-lsp /usr/local/bin
```
Note: To activate properly nvim needs to know the jq filetype.
You can add it via:
```lua
docs: update configs.md skip-checks: true
2024-10-15 16:02:50 +00:00
vim.cmd([[au BufRead,BufNewFile *.jq setfiletype jq]])
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jqls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "jq-lsp" }
```
- `filetypes` :
```lua
{ "jq" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jqls.lua:2](../lua/lspconfig/configs/jqls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jsonls
https://github.com/hrsh7th/vscode-langservers-extracted
vscode-json-language-server, a language server for JSON and JSON schema
`vscode-json-language-server` can be installed via `npm`:
```sh
npm i -g vscode-langservers-extracted
```
`vscode-json-language-server` only provides completions when snippet support is enabled. If you use Neovim older than v0.10 you need to enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.
```lua
--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true
require'lspconfig'.jsonls.setup {
capabilities = capabilities,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jsonls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscode-json-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "json", "jsonc" }
```
- `init_options` :
```lua
{
provideFormatter = true
}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jsonls.lua:2](../lua/lspconfig/configs/jsonls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## jsonnet_ls
https://github.com/grafana/jsonnet-language-server
A Language Server Protocol (LSP) server for Jsonnet.
The language server can be installed with `go`:
```sh
go install github.com/grafana/jsonnet-language-server@latest
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.jsonnet_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "jsonnet-language-server" }
```
- `filetypes` :
```lua
{ "jsonnet", "libsonnet" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/jsonnet_ls.lua:13](../lua/lspconfig/configs/jsonnet_ls.lua#L13)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/jsonnet_ls.lua:13](../lua/lspconfig/configs/jsonnet_ls.lua#L13)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## julials
https://github.com/julia-vscode/julia-vscode
LanguageServer.jl can be installed with `julia` and `Pkg`:
```sh
julia --project=~/.julia/environments/nvim-lspconfig -e 'using Pkg; Pkg.add("LanguageServer")'
```
where `~/.julia/environments/nvim-lspconfig` is the location where
the default configuration expects LanguageServer.jl to be installed.
To update an existing install, use the following command:
```sh
julia --project=~/.julia/environments/nvim-lspconfig -e 'using Pkg; Pkg.update()'
```
Note: In order to have LanguageServer.jl pick up installed packages or dependencies in a
Julia project, you must make sure that the project is instantiated:
```sh
julia --project=/path/to/my/project -e 'using Pkg; Pkg.instantiate()'
```
Note: The julia programming language searches for global environments within the `environments/`
folder of `$JULIA_DEPOT_PATH` entries. By default this simply `~/.julia/environments`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.julials.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- JuliaActivateEnv: Activate a Julia environment
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "julia", "--startup-file=no", "--history-file=no", "-e", ' # Load LanguageServer.jl: attempt to load from ~/.julia/environments/nvim-lspconfig\n # with the regular load path as a fallback\n ls_install_path = joinpath(\n get(DEPOT_PATH, 1, joinpath(homedir(), ".julia")),\n "environments", "nvim-lspconfig"\n )\n pushfirst!(LOAD_PATH, ls_install_path)\n using LanguageServer\n popfirst!(LOAD_PATH)\n depot_path = get(ENV, "JULIA_DEPOT_PATH", "")\n project_path = let\n dirname(something(\n ## 1. Finds an explicitly set project (JULIA_PROJECT)\n Base.load_path_expand((\n p = get(ENV, "JULIA_PROJECT", nothing);\n p === nothing ? nothing : isempty(p) ? nothing : p\n )),\n ## 2. Look for a Project.toml file in the current working directory,\n ## or parent directories, with $HOME as an upper boundary\n Base.current_project(),\n ## 3. First entry in the load path\n get(Base.load_path(), 1, nothing),\n ## 4. Fallback to default global environment,\n ## this is more or less unreachable\n Base.load_path_expand("@v#.#"),\n ))\n end\n @info "Running language server" VERSION pwd() project_path depot_path\n server = LanguageServer.LanguageServerInstance(stdin, stdout, project_path, depot_path)\n server.runlinter = true\n run(server)\n ' }
```
- `filetypes` :
```lua
{ "julia" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/julials.lua:97](../lua/lspconfig/configs/julials.lua#L97)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## kcl
https://github.com/kcl-lang/kcl.nvim
Language server for the KCL configuration and policy language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.kcl.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "kcl-language-server" }
```
- `filetypes` :
```lua
{ "kcl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/kcl.lua:4](../lua/lspconfig/configs/kcl.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## koka
regen docs
2024-10-24 15:06:10 +00:00
https://koka-lang.github.io/koka/doc/index.html
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
Koka is a functional programming language with effect types and handlers.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.koka.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "koka", "--language-server", "--lsstdio" }
```
- `filetypes` :
```lua
{ "koka" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/koka.lua:2](../lua/lspconfig/configs/koka.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## kotlin_language_server
regen docs
2024-10-24 15:06:10 +00:00
A kotlin language server which was developed for internal usage and
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
released afterwards. Maintaining is not done by the original author,
but by fwcd.
It is built via gradle and developed on github.
Source and additional description:
https://github.com/fwcd/kotlin-language-server
This server requires vim to be aware of the kotlin-filetype.
You could refer for this capability to:
https://github.com/udalov/kotlin-vim (recommended)
Note that there is no LICENSE specified yet.
For faster startup, you can setup caching by specifying a storagePath
in the init_options. The default is your home directory.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.kotlin_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "kotlin-language-server" }
```
- `filetypes` :
```lua
{ "kotlin" }
```
- `init_options` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-11 14:37:54 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/kotlin_language_server.lua:20](../lua/lspconfig/configs/kotlin_language_server.lua#L20)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-07 05:17:58 +00:00
## kulala_ls
https://github.com/mistweaverco/kulala-ls
A minimal language server for HTTP syntax.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-07 05:17:58 +00:00
```lua
require'lspconfig'.kulala_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "kulala-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "http" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/kulala_ls.lua:2](../lua/lspconfig/configs/kulala_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-07 05:17:58 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lean3ls
https://github.com/leanprover/lean-client-js/tree/master/lean-language-server
Lean installation instructions can be found
[here](https://leanprover-community.github.io/get_started.html#regular-install).
Once Lean is installed, you can install the Lean 3 language server by running
```sh
npm install -g lean-language-server
```
Note: that if you're using [lean.nvim](https://github.com/Julian/lean.nvim),
that plugin fully handles the setup of the Lean language server,
and you shouldn't set up `lean3ls` both with it and `lspconfig`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lean3ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lean-language-server", "--stdio", "--", "-M", "4096", "-T", "100000" }
```
- `filetypes` :
```lua
{ "lean3" }
```
- `offset_encoding` :
```lua
"utf-32"
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lean3ls.lua:4](../lua/lspconfig/configs/lean3ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## leanls
https://github.com/leanprover/lean4
Lean installation instructions can be found
[here](https://leanprover-community.github.io/get_started.html#regular-install).
The Lean language server is included in any Lean installation and
does not require any additional packages.
Note: that if you're using [lean.nvim](https://github.com/Julian/lean.nvim),
that plugin fully handles the setup of the Lean language server,
and you shouldn't set up `leanls` both with it and `lspconfig`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.leanls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lake", "serve", "--" }
```
- `filetypes` :
```lua
{ "lean" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/leanls.lua:4](../lua/lspconfig/configs/leanls.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/leanls.lua:4](../lua/lspconfig/configs/leanls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lelwel_ls
https://github.com/0x2a-42/lelwel
Language server for lelwel grammars.
You can install `lelwel-ls` via cargo:
```sh
cargo install --features="lsp" lelwel
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lelwel_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lelwel-ls" }
```
- `filetypes` :
```lua
{ "llw" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lelwel_ls.lua:2](../lua/lspconfig/configs/lelwel_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lemminx
https://github.com/eclipse/lemminx
The easiest way to install the server is to get a binary from https://github.com/redhat-developer/vscode-xml/releases and place it on your PATH.
NOTE to macOS users: Binaries from unidentified developers are blocked by default. If you trust the downloaded binary, run it once, cancel the prompt, then remove the binary from Gatekeeper quarantine with `xattr -d com.apple.quarantine lemminx`. It should now run without being blocked.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lemminx.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lemminx" }
```
- `filetypes` :
```lua
{ "xml", "xsd", "xsl", "xslt", "svg" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lemminx.lua:2](../lua/lspconfig/configs/lemminx.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lexical
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/lexical-lsp/lexical
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Lexical is a next-generation language server for the Elixir programming language.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Follow the [Detailed Installation Instructions](https://github.com/lexical-lsp/lexical/blob/main/pages/installation.md)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
**By default, `lexical` doesn't have a `cmd` set.**
This is because nvim-lspconfig does not make assumptions about your path.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lexical.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "elixir", "eelixir", "heex", "surface" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lexical.lua:4](../lua/lspconfig/configs/lexical.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-09 08:28:36 +00:00
## lsp_ai
docs: update configs.md skip-checks: true
2024-10-11 05:28:48 +00:00
https://github.com/SilasMarvin/lsp-ai
LSP-AI is an open source language server that serves as a backend for AI-powered functionality in your favorite code
editors. It offers features like in-editor chatting with LLMs and code completions.
You will need to provide configuration for the inference backends and models you want to use, as well as configure
completion/code actions. See the [wiki docs](https://github.com/SilasMarvin/lsp-ai/wiki/Configuration) and
[examples](https://github.com/SilasMarvin/lsp-ai/blob/main/examples/nvim) for more information.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-09 08:28:36 +00:00
```lua
require'lspconfig'.lsp_ai.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lsp-ai" }
```
- `filetypes` :
```lua
{}
```
- `init_options` :
```lua
{
memory = {
file_store = vim.empty_dict()
},
models = vim.empty_dict()
}
```
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-09 08:28:36 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ltex
https://github.com/valentjn/ltex-ls
LTeX Language Server: LSP language server for LanguageTool 🔍✔️ with support for LaTeX 🎓, Markdown 📝, and others
To install, download the latest [release](https://github.com/valentjn/ltex-ls/releases) and ensure `ltex-ls` is on your path.
This server accepts configuration via the `settings` key.
```lua
settings = {
ltex = {
language = "en-GB",
},
},
```
To support org files or R sweave, users can define a custom filetype autocommand (or use a plugin which defines these filetypes):
```lua
vim.cmd [[ autocmd BufRead,BufNewFile *.org set filetype=org ]]
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ltex.setup{}
regen docs
2024-10-24 15:06:10 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ltex-ls" }
```
- `filetypes` :
```lua
{ "bib", "gitcommit", "markdown", "org", "plaintex", "rst", "rnoweb", "tex", "pandoc", "quarto", "rmd", "context", "html", "xhtml", "mail", "text" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `get_language_id` source (use "gF" to visit): [../lua/lspconfig/configs/ltex.lua:51](../lua/lspconfig/configs/ltex.lua#L51)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ltex.lua:51](../lua/lspconfig/configs/ltex.lua#L51)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
ltex = {
enabled = { "bibtex", "gitcommit", "markdown", "org", "tex", "restructuredtext", "rsweave", "latex", "quarto", "rmd", "context", "html", "xhtml", "mail", "plaintext" }
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-07 13:10:51 +00:00
## ltex_plus
https://github.com/ltex-plus/ltex-ls-plus
LTeX Language Server: LSP language server for LanguageTool 🔍✔️ with support for LaTeX 🎓, Markdown 📝, and others
To install, download the latest [release](https://github.com/ltex-plus/ltex-ls-plus) and ensure `ltex-ls-plus` is on your path.
This server accepts configuration via the `settings` key.
```lua
settings = {
ltex = {
language = "en-GB",
},
},
```
To support org files or R sweave, users can define a custom filetype autocommand (or use a plugin which defines these filetypes):
```lua
vim.cmd [[ autocmd BufRead,BufNewFile *.org set filetype=org ]]
```
Snippet to enable the language server:
```lua
require'lspconfig'.ltex_plus.setup{}
```
Default config:
- `cmd` :
```lua
{ "ltex-ls-plus" }
```
- `filetypes` :
```lua
{ "bib", "context", "gitcommit", "html", "markdown", "org", "pandoc", "plaintex", "quarto", "mail", "mdx", "rmd", "rnoweb", "rst", "tex", "text", "typst", "xhtml" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `get_language_id` source (use "gF" to visit): [../lua/lspconfig/configs/ltex_plus.lua:16](../lua/lspconfig/configs/ltex_plus.lua#L16)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ltex_plus.lua:16](../lua/lspconfig/configs/ltex_plus.lua#L16)
docs: update configs.md skip-checks: true
2024-12-07 13:10:51 +00:00
- `settings` :
```lua
{
ltex = {
enabled = { "bib", "context", "gitcommit", "html", "markdown", "org", "pandoc", "plaintex", "quarto", "mail", "mdx", "rmd", "rnoweb", "rst", "tex", "text", "typst", "xhtml" }
}
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lua_ls
https://github.com/luals/lua-language-server
Lua language server.
`lua-language-server` can be installed by following the instructions [here](https://luals.github.io/#neovim-install).
The default `cmd` assumes that the `lua-language-server` binary can be found in `$PATH`.
If you primarily use `lua-language-server` for Neovim, and want to provide completions,
analysis, and location handling for plugins on runtime path, you can use the following
settings.
```lua
require'lspconfig'.lua_ls.setup {
on_init = function(client)
if client.workspace_folders then
local path = client.workspace_folders[1].name
docs: update configs.md skip-checks: true
2024-12-02 10:12:49 +00:00
if vim.loop.fs_stat(path..'/.luarc.json') or vim.loop.fs_stat(path..'/.luarc.jsonc') then
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
return
end
end
client.config.settings.Lua = vim.tbl_deep_extend('force', client.config.settings.Lua, {
runtime = {
-- Tell the language server which version of Lua you're using
-- (most likely LuaJIT in the case of Neovim)
version = 'LuaJIT'
},
-- Make the server aware of Neovim runtime files
workspace = {
checkThirdParty = false,
library = {
vim.env.VIMRUNTIME
-- Depending on the usage, you might want to add additional paths here.
-- "${3rd}/luv/library"
-- "${3rd}/busted/library",
}
docs: update configs.md skip-checks: true
2024-10-18 13:02:59 +00:00
-- or pull in all of 'runtimepath'. NOTE: this is a lot slower and will cause issues when working on your own configuration (see https://github.com/neovim/nvim-lspconfig/issues/3189)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
-- library = vim.api.nvim_get_runtime_file("", true)
}
})
end,
settings = {
Lua = {}
}
}
```
See `lua-language-server`'s [documentation](https://luals.github.io/wiki/settings/) for an explanation of the above fields:
* [Lua.runtime.path](https://luals.github.io/wiki/settings/#runtimepath)
* [Lua.workspace.library](https://luals.github.io/wiki/settings/#workspacelibrary)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lua_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lua-language-server" }
```
- `filetypes` :
```lua
{ "lua" }
```
- `log_level` :
```lua
2
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lua_ls.lua:14](../lua/lspconfig/configs/lua_ls.lua#L14)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## luau_lsp
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.luau_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "luau-lsp", "lsp" }
```
- `filetypes` :
```lua
{ "luau" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/luau_lsp.lua:2](../lua/lspconfig/configs/luau_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## lwc_ls
https://github.com/forcedotcom/lightning-language-server/
Language server for Lightning Web Components.
For manual installation, utilize the official [NPM package](https://www.npmjs.com/package/@salesforce/lwc-language-server).
Then, configure `cmd` to run the Node script at the unpacked location:
```lua
require'lspconfig'.lwc_ls.setup {
cmd = {
'node',
'/path/to/node_modules/@salesforce/lwc-language-server/bin/lwc-language-server.js',
'--stdio'
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.lwc_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "lwc-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "javascript", "html" }
```
- `init_options` :
```lua
{
embeddedLanguages = {
javascript = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/lwc_ls.lua:4](../lua/lspconfig/configs/lwc_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## m68k
https://github.com/grahambates/m68k-lsp
Language server for Motorola 68000 family assembly
`m68k-lsp-server` can be installed via `npm`:
```sh
npm install -g m68k-lsp-server
```
Ensure you are using the 68k asm syntax variant in Neovim.
```lua
vim.g.asmsyntax = 'asm68k'
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.m68k.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "m68k-lsp-server", "--stdio" }
```
- `filetypes` :
```lua
{ "asm68k" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/m68k.lua:4](../lua/lspconfig/configs/m68k.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## markdown_oxide
https://github.com/Feel-ix-343/markdown-oxide
Editor Agnostic PKM: you bring the text editor and we
bring the PKM.
Inspired by and compatible with Obsidian.
Check the readme to see how to properly setup.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.markdown_oxide.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- Today: Open today's daily note
- Tomorrow: Open tomorrow's daily note
- Yesterday: Open yesterday's daily note
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "markdown-oxide" }
```
- `filetypes` :
```lua
{ "markdown" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/markdown_oxide.lua:2](../lua/lspconfig/configs/markdown_oxide.lua#L2)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-04 05:36:35 +00:00
## marko-js
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/marko-js/language-server
docs: update configs.md skip-checks: true
2024-10-04 05:36:35 +00:00
Using the Language Server Protocol to improve Marko's developer experience.
Can be installed via npm:
```
npm i -g @marko/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-04 05:36:35 +00:00
```lua
require'lspconfig'.marko-js.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "marko-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "marko" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/marko-js.lua:2](../lua/lspconfig/configs/marko-js.lua#L2)
docs: update configs.md skip-checks: true
2024-10-04 05:36:35 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## marksman
https://github.com/artempyanykh/marksman
Marksman is a Markdown LSP server providing completion, cross-references, diagnostics, and more.
Marksman works on MacOS, Linux, and Windows and is distributed as a self-contained binary for each OS.
Pre-built binaries can be downloaded from https://github.com/artempyanykh/marksman/releases
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.marksman.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "marksman", "server" }
```
- `filetypes` :
```lua
{ "markdown", "markdown.mdx" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/marksman.lua:7](../lua/lspconfig/configs/marksman.lua#L7)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## matlab_ls
https://github.com/mathworks/MATLAB-language-server
MATLAB® language server implements the Microsoft® Language Server Protocol for the MATLAB language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.matlab_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "matlab-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "matlab" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/matlab_ls.lua:2](../lua/lspconfig/configs/matlab_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
MATLAB = {
indexWorkspace = false,
installPath = "",
matlabConnectionTiming = "onStart",
telemetry = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `false`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mdx_analyzer
https://github.com/mdx-js/mdx-analyzer
`mdx-analyzer`, a language server for MDX
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mdx_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mdx-language-server", "--stdio" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-12-25 10:37:15 +00:00
{ "mdx" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `init_options` :
```lua
{
typescript = {}
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/mdx_analyzer.lua:9](../lua/lspconfig/configs/mdx_analyzer.lua#L9)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mdx_analyzer.lua:9](../lua/lspconfig/configs/mdx_analyzer.lua#L9)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mesonlsp
https://github.com/JCWasmx86/mesonlsp
An unofficial, unendorsed language server for meson written in C++
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
require'lspconfig'.mesonlsp.setup{}
```
Default config:
- `cmd` :
```lua
{ "mesonlsp", "--lsp" }
```
- `filetypes` :
```lua
{ "meson" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mesonlsp.lua:4](../lua/lspconfig/configs/mesonlsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## metals
https://scalameta.org/metals/
Scala language server with rich IDE features.
See full instructions in the Metals documentation:
https://scalameta.org/metals/docs/editors/vim#using-an-alternative-lsp-client
Note: that if you're using [nvim-metals](https://github.com/scalameta/nvim-metals), that plugin fully handles the setup and installation of Metals, and you shouldn't set up Metals both with it and `lspconfig`.
To install Metals, make sure to have [coursier](https://get-coursier.io/docs/cli-installation) installed, and once you do you can install the latest Metals with `cs install metals`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.metals.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `capabilities` :
```lua
{
workspace = {
configuration = false
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "metals" }
```
- `filetypes` :
```lua
{ "scala" }
```
- `init_options` :
```lua
{
compilerOptions = {
snippetAutoIndent = false
},
isHttpEnabled = true,
statusBarProvider = "show-message"
}
```
- `message_level` :
```lua
4
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/metals.lua:4](../lua/lspconfig/configs/metals.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## millet
https://github.com/azdavis/millet
Millet, a language server for Standard ML
To use with nvim:
1. Install a Rust toolchain: https://rustup.rs
2. Clone the repo
3. Run `cargo build --release --bin lang-srv`
4. Move `target/release/lang-srv` to somewhere on your $PATH as `millet`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.millet.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "millet" }
```
- `filetypes` :
```lua
{ "sml" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/millet.lua:4](../lua/lspconfig/configs/millet.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mint
https://www.mint-lang.com
Install Mint using the [instructions](https://www.mint-lang.com/install).
The language server is included since version 0.12.0.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mint.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mint", "ls" }
```
- `filetypes` :
```lua
{ "mint" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mint.lua:4](../lua/lspconfig/configs/mint.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mlir_lsp_server
https://mlir.llvm.org/docs/Tools/MLIRLSP/#mlir-lsp-language-server--mlir-lsp-server=
The Language Server for the LLVM MLIR language
`mlir-lsp-server` can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mlir_lsp_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mlir-lsp-server" }
```
- `filetypes` :
```lua
{ "mlir" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mlir_lsp_server.lua:2](../lua/lspconfig/configs/mlir_lsp_server.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mlir_pdll_lsp_server
https://mlir.llvm.org/docs/Tools/MLIRLSP/#pdll-lsp-language-server--mlir-pdll-lsp-server
The Language Server for the LLVM PDLL language
`mlir-pdll-lsp-server` can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mlir_pdll_lsp_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mlir-pdll-lsp-server" }
```
- `filetypes` :
```lua
{ "pdll" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mlir_pdll_lsp_server.lua:4](../lua/lspconfig/configs/mlir_pdll_lsp_server.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mm0_ls
https://github.com/digama0/mm0
Language Server for the metamath-zero theorem prover.
Requires [mm0-rs](https://github.com/digama0/mm0/tree/master/mm0-rs) to be installed
and available on the `PATH`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mm0_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mm0-rs", "server" }
```
- `filetypes` :
```lua
{ "metamath-zero" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mm0_ls.lua:2](../lua/lspconfig/configs/mm0_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mojo
https://github.com/modularml/mojo
`mojo-lsp-server` can be installed [via Modular](https://developer.modular.com/download)
Mojo is a new programming language that bridges the gap between research and production by combining Python syntax and ecosystem with systems programming and metaprogramming features.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mojo.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mojo-lsp-server" }
```
- `filetypes` :
```lua
{ "mojo" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mojo.lua:2](../lua/lspconfig/configs/mojo.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## motoko_lsp
https://github.com/dfinity/vscode-motoko
Language server for the Motoko programming language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.motoko_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "motoko-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "motoko" }
```
- `init_options` :
```lua
{
formatter = "auto"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/motoko_lsp.lua:4](../lua/lspconfig/configs/motoko_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## move_analyzer
https://github.com/move-language/move/tree/main/language/move-analyzer
Language server for Move
The `move-analyzer` can be installed by running:
```
cargo install --git https://github.com/move-language/move move-analyzer
```
See [`move-analyzer`'s doc](https://github.com/move-language/move/blob/1b258a06e3c7d2bc9174578aac92cca3ac19de71/language/move-analyzer/editors/code/README.md#how-to-install) for details.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.move_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "move-analyzer" }
```
- `filetypes` :
```lua
{ "move" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/move_analyzer.lua:4](../lua/lspconfig/configs/move_analyzer.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## msbuild_project_tools_server
https://github.com/tintoy/msbuild-project-tools-server/
MSBuild Project Tools Server can be installed by following the README.MD on the above repository.
Example config:
```lua
lspconfig.msbuild_project_tools_server.setup {
cmd = {'dotnet', '/path/to/server/MSBuildProjectTools.LanguageServer.Host.dll'}
}
```
docs: update configs.md skip-checks: true
2024-12-17 07:22:31 +00:00
There's no builtin filetypes for msbuild files, would require some filetype aliases:
```lua
vim.filetype.add({
extension = {
props = 'msbuild',
tasks = 'msbuild',
targets = 'msbuild',
},
pattern = {
[ [[.*\..*proj]] ] = 'msbuild',
},
})
```
Optionally tell treesitter to treat `msbuild` as `xml` so you can get syntax highlighting if you have the treesitter-xml-parser installed.
```lua
vim.treesitter.language.register('xml', { 'msbuild' })
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.msbuild_project_tools_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "dotnet", "MSBuildProjectTools.LanguageServer.Host.dll" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-12-17 07:22:31 +00:00
{ "msbuild" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `init_options` :
```lua
{}
```
docs: update configs.md skip-checks: true
2025-01-05 13:42:44 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/msbuild_project_tools_server.lua:5](../lua/lspconfig/configs/msbuild_project_tools_server.lua#L5)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## mutt_ls
https://github.com/neomutt/mutt-language-server
A language server for (neo)mutt's muttrc. It can be installed via pip.
```sh
pip install mutt-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.mutt_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "mutt-language-server" }
```
- `filetypes` :
```lua
{ "muttrc", "neomuttrc" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/mutt_ls.lua:2](../lua/lspconfig/configs/mutt_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nelua_lsp
https://github.com/codehz/nelua-lsp
nelua-lsp is an experimental nelua language server.
You need [nelua.vim](https://github.com/stefanos82/nelua.vim/blob/main/ftdetect/nelua.vim) for nelua files to be recognized or add this to your config:
in vimscript:
```vimscript
au BufNewFile,BufRead *.nelua setf nelua
```
in lua:
```lua
vim.api.nvim_create_autocmd({ "BufNewFile", "BufRead" }, { pattern = { "*.nelua" }, command = "setf nelua"})
```
**By default, nelua-lsp doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set `cmd` to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.
```lua
require'lspconfig'.nelua_lsp.setup {
cmd = { "nelua", "-L", "/path/to/nelua-lsp/", "--script", "/path/to/nelua-lsp/nelua-lsp.lua" },
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nelua_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "nelua" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nelua_lsp.lua:4](../lua/lspconfig/configs/nelua_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## neocmake
https://github.com/Decodetalkers/neocmakelsp
CMake LSP Implementation
Neovim does not currently include built-in snippets. `neocmakelsp` only provides completions when snippet support is enabled. To enable completion, install a snippet plugin and add the following override to your language client capabilities during setup.
```lua
--Enable (broadcasting) snippet capability for completion
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities.textDocument.completion.completionItem.snippetSupport = true
require'lspconfig'.neocmake.setup {
capabilities = capabilities,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.neocmake.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "neocmakelsp", "--stdio" }
```
- `filetypes` :
```lua
{ "cmake" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/neocmake.lua:4](../lua/lspconfig/configs/neocmake.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-11-07 11:25:46 +00:00
## nextflow_ls
https://github.com/nextflow-io/language-server
Requirements:
- Java 17+
`nextflow_ls` can be installed by following the instructions [here](https://github.com/nextflow-io/language-server#development).
If you have installed nextflow language server, you can set the `cmd` custom path as follow:
```lua
require'lspconfig'.nextflow_ls.setup{
cmd = { 'java', '-jar', 'nextflow-language-server-all.jar' },
filetypes = { 'nextflow' },
root_dir = util.root_pattern('nextflow.config', '.git'),
settings = {
nextflow = {
files = {
exclude = { '.git', '.nf-test', 'work' },
},
},
},
}
```
Snippet to enable the language server:
```lua
require'lspconfig'.nextflow_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "java", "-jar", "nextflow-language-server-all.jar" }
```
- `filetypes` :
```lua
{ "nextflow" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nextflow_ls.lua:4](../lua/lspconfig/configs/nextflow_ls.lua#L4)
- `settings` :
```lua
{
nextflow = {
files = {
exclude = { ".git", ".nf-test", "work" }
}
}
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nextls
https://github.com/elixir-tools/next-ls
**By default, next-ls does not set its `cmd`. Please see the following [detailed instructions](https://www.elixir-tools.dev/docs/next-ls/installation/) for possible installation methods.**
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nextls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "elixir", "eelixir", "heex", "surface" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nextls.lua:4](../lua/lspconfig/configs/nextls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nginx_language_server
https://pypi.org/project/nginx-language-server/
`nginx-language-server` can be installed via pip:
```sh
pip install -U nginx-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nginx_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nginx-language-server" }
```
- `filetypes` :
```lua
{ "nginx" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nginx_language_server.lua:4](../lua/lspconfig/configs/nginx_language_server.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nickel_ls
Nickel Language Server
https://github.com/tweag/nickel
`nls` can be installed with nix, or cargo, from the Nickel repository.
```sh
git clone https://github.com/tweag/nickel.git
```
Nix:
```sh
cd nickel
nix-env -f . -i
```
cargo:
```sh
cd nickel/lsp/nls
cargo install --path .
```
In order to have lspconfig detect Nickel filetypes (a prerequisite for autostarting a server),
install the [Nickel vim plugin](https://github.com/nickel-lang/vim-nickel).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nickel_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nls" }
```
- `filetypes` :
```lua
{ "ncl", "nickel" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nickel_ls.lua:2](../lua/lspconfig/configs/nickel_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nil_ls
https://github.com/oxalica/nil
A new language server for Nix Expression Language.
If you are using Nix with Flakes support, run `nix profile install github:oxalica/nil` to install.
Check the repository README for more information.
_See an example config at https://github.com/oxalica/nil/blob/main/dev/nvim-lsp.nix._
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nil_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nil" }
```
- `filetypes` :
```lua
{ "nix" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nil_ls.lua:4](../lua/lspconfig/configs/nil_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nim_langserver
https://github.com/nim-lang/langserver
`nim-langserver` can be installed via the `nimble` package manager:
```sh
nimble install nimlangserver
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nim_langserver.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nimlangserver" }
```
- `filetypes` :
```lua
{ "nim" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nim_langserver.lua:4](../lua/lspconfig/configs/nim_langserver.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nimls
https://github.com/PMunch/nimlsp
`nimlsp` can be installed via the `nimble` package manager:
```sh
nimble install nimlsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nimls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nimlsp" }
```
- `filetypes` :
```lua
{ "nim" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nimls.lua:4](../lua/lspconfig/configs/nimls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nixd
https://github.com/nix-community/nixd
Nix language server, based on nix libraries.
If you are using Nix with Flakes support, run `nix profile install github:nix-community/nixd` to install.
Check the repository README for more information.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nixd.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nixd" }
```
- `filetypes` :
```lua
{ "nix" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nixd.lua:4](../lua/lspconfig/configs/nixd.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nomad_lsp
https://github.com/juliosueiras/nomad-lsp
Written in Go, compilation is needed for `nomad_lsp` to be used. Please see the [original repository](https://github.com/juliosuieras/nomad-lsp).
Add the executable to your system or vim PATH and it will be set to go.
No configuration option is needed unless you choose not to add `nomad-lsp` executable to the PATH. You should know what you are doing if you choose so.
```lua
require('lspconfig').nomad_lsp.setup{ }
```
However, a `hcl.nomad` or `nomad` filetype should be defined.
Description of your jobs should be written in `.nomad` files for the LSP client to configure the server's `root_dir` configuration option.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nomad_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nomad-lsp" }
```
- `filetypes` :
```lua
{ "hcl.nomad", "nomad" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nomad_lsp.lua:9](../lua/lspconfig/configs/nomad_lsp.lua#L9)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ntt
https://github.com/nokia/ntt
Installation instructions can be found [here](https://github.com/nokia/ntt#Install).
Can be configured by passing a "settings" object to `ntt.setup{}`:
```lua
require('lspconfig').ntt.setup{
settings = {
ntt = {
}
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ntt.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ntt", "langserver" }
```
- `filetypes` :
```lua
{ "ttcn" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ntt.lua:5](../lua/lspconfig/configs/ntt.lua#L5)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nushell
https://github.com/nushell/nushell
Nushell built-in language server.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nushell.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nu", "--lsp" }
```
- `filetypes` :
```lua
{ "nu" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nushell.lua:2](../lua/lspconfig/configs/nushell.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## nxls
https://github.com/nrwl/nx-console/tree/master/apps/nxls
nxls, a language server for Nx Workspaces
`nxls` can be installed via `npm`:
```sh
npm i -g nxls
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.nxls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nxls", "--stdio" }
```
- `filetypes` :
```lua
{ "json", "jsonc" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/nxls.lua:4](../lua/lspconfig/configs/nxls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ocamlls
https://github.com/ocaml-lsp/ocaml-language-server
`ocaml-language-server` can be installed via `npm`
```sh
npm install -g ocaml-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ocamlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ocaml-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "ocaml", "reason" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ocamlls.lua:4](../lua/lspconfig/configs/ocamlls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ocamllsp
https://github.com/ocaml/ocaml-lsp
`ocaml-lsp` can be installed as described in [installation guide](https://github.com/ocaml/ocaml-lsp#installation).
To install the lsp server in a particular opam switch:
```sh
opam install ocaml-lsp-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ocamllsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ocamllsp" }
```
- `filetypes` :
```lua
{ "ocaml", "menhir", "ocamlinterface", "ocamllex", "reason", "dune" }
```
- `get_language_id` source (use "gF" to visit): [../lua/lspconfig/configs/ocamllsp.lua:17](../lua/lspconfig/configs/ocamllsp.lua#L17)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ocamllsp.lua:17](../lua/lspconfig/configs/ocamllsp.lua#L17)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ols
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/DanielGavin/ols
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
`Odin Language Server`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ols.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ols" }
```
- `filetypes` :
```lua
{ "odin" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ols.lua:4](../lua/lspconfig/configs/ols.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## omnisharp
https://github.com/omnisharp/omnisharp-roslyn
OmniSharp server based on Roslyn workspaces
`omnisharp-roslyn` can be installed by downloading and extracting a release from [here](https://github.com/OmniSharp/omnisharp-roslyn/releases).
OmniSharp can also be built from source by following the instructions [here](https://github.com/omnisharp/omnisharp-roslyn#downloading-omnisharp).
OmniSharp requires the [dotnet-sdk](https://dotnet.microsoft.com/download) to be installed.
**By default, omnisharp-roslyn doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path. You must add the following to your init.vim or init.lua to set `cmd` to the absolute path ($HOME and ~ are not expanded) of the unzipped run script or binary.
For `go_to_definition` to work fully, extended `textDocument/definition` handler is needed, for example see [omnisharp-extended-lsp.nvim](https://github.com/Hoffs/omnisharp-extended-lsp.nvim)
```lua
require'lspconfig'.omnisharp.setup {
cmd = { "dotnet", "/path/to/omnisharp/OmniSharp.dll" },
settings = {
FormattingOptions = {
-- Enables support for reading code style, naming convention and analyzer
-- settings from .editorconfig.
EnableEditorConfigSupport = true,
-- Specifies whether 'using' directives should be grouped and sorted during
-- document formatting.
OrganizeImports = nil,
},
MsBuild = {
-- If true, MSBuild project system will only load projects for files that
-- were opened in the editor. This setting is useful for big C# codebases
-- and allows for faster initialization of code navigation features only
-- for projects that are relevant to code that is being edited. With this
-- setting enabled OmniSharp may load fewer projects and may thus display
-- incomplete reference lists for symbols.
LoadProjectsOnDemand = nil,
},
RoslynExtensionsOptions = {
-- Enables support for roslyn analyzers, code fixes and rulesets.
EnableAnalyzersSupport = nil,
-- Enables support for showing unimported types and unimported extension
-- methods in completion lists. When committed, the appropriate using
-- directive will be added at the top of the current file. This option can
-- have a negative impact on initial completion responsiveness,
-- particularly for the first few completion sessions after opening a
-- solution.
EnableImportCompletion = nil,
-- Only run analyzers against open files when 'enableRoslynAnalyzers' is
-- true
AnalyzeOpenDocumentsOnly = nil,
},
Sdk = {
-- Specifies whether to include preview versions of the .NET SDK when
-- determining which version to use for project loading.
IncludePrereleases = true,
},
},
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.omnisharp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "cs", "vb" }
```
- `init_options` :
```lua
{}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/omnisharp.lua:4](../lua/lspconfig/configs/omnisharp.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/omnisharp.lua:4](../lua/lspconfig/configs/omnisharp.lua#L4)
- `settings` :
```lua
{
FormattingOptions = {
EnableEditorConfigSupport = true
},
MsBuild = {},
RoslynExtensionsOptions = {},
Sdk = {
IncludePrereleases = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## opencl_ls
https://github.com/Galarius/opencl-language-server
Build instructions can be found [here](https://github.com/Galarius/opencl-language-server/blob/main/_dev/build.md).
Prebuilt binaries are available for Linux, macOS and Windows [here](https://github.com/Galarius/opencl-language-server/releases).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.opencl_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "opencl-language-server" }
```
- `filetypes` :
```lua
{ "opencl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/opencl_ls.lua:2](../lua/lspconfig/configs/opencl_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## openedge_ls
[Language server](https://github.com/vscode-abl/vscode-abl) for Progress OpenEdge ABL.
For manual installation, download abl-lsp.jar from the [VSCode
extension](https://github.com/vscode-abl/vscode-abl/releases/latest).
Configuration
```lua
require('lspconfig').['openedge_ls'].setup {
oe_jar_path = '/path/to/abl-lsp.jar',
dlc = '12.2:/path/to/dlc-12.2', -- Version number and OpenEdge root directory (colon separator)
debug = false, -- Set to true for debug logging
trace = false -- Set to true for trace logging (REALLY verbose)
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.openedge_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "progress" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/openedge_ls.lua:4](../lua/lspconfig/configs/openedge_ls.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/openedge_ls.lua:4](../lua/lspconfig/configs/openedge_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## openscad_ls
https://github.com/dzhu/openscad-language-server
A Language Server Protocol server for OpenSCAD
You can build and install `openscad-language-server` binary with `cargo`:
```sh
cargo install openscad-language-server
```
Vim does not have built-in syntax for the `openscad` filetype currently.
This can be added via an autocmd:
```lua
vim.cmd [[ autocmd BufRead,BufNewFile *.scad set filetype=openscad ]]
```
or by installing a filetype plugin such as https://github.com/sirtaj/vim-openscad
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.openscad_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "openscad-language-server" }
```
- `filetypes` :
```lua
{ "openscad" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/openscad_ls.lua:2](../lua/lspconfig/configs/openscad_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## openscad_lsp
https://github.com/Leathong/openscad-LSP
A Language Server Protocol server for OpenSCAD
You can build and install `openscad-lsp` binary with `cargo`:
```sh
cargo install openscad-lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.openscad_lsp.setup{}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
Default config:
- `cmd` :
```lua
{ "openscad-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "openscad" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/openscad_lsp.lua:2](../lua/lspconfig/configs/openscad_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pact_ls
https://github.com/kadena-io/pact-lsp
The Pact language server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pact_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pact-lsp" }
```
- `filetypes` :
```lua
{ "pact" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pact_ls.lua:2](../lua/lspconfig/configs/pact_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pasls
https://github.com/genericptr/pascal-language-server
An LSP server implementation for Pascal variants that are supported by Free Pascal, including Object Pascal. It uses CodeTools from Lazarus as backend.
First set `cmd` to the Pascal lsp binary.
Customization options are passed to pasls as environment variables for example in your `.bashrc`:
```bash
export FPCDIR='/usr/lib/fpc/src' # FPC source directory (This is the only required option for the server to work).
export PP='/usr/lib/fpc/3.2.2/ppcx64' # Path to the Free Pascal compiler executable.
export LAZARUSDIR='/usr/lib/lazarus' # Path to the Lazarus sources.
export FPCTARGET='' # Target operating system for cross compiling.
export FPCTARGETCPU='x86_64' # Target CPU for cross compiling.
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pasls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pasls" }
```
- `filetypes` :
```lua
{ "pascal" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pasls.lua:4](../lua/lspconfig/configs/pasls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pbls
https://git.sr.ht/~rrc/pbls
Prerequisites: Ensure protoc is on your $PATH.
`pbls` can be installed via `cargo install`:
```sh
cargo install --git https://git.sr.ht/~rrc/pbls
```
pbls is a Language Server for protobuf
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pbls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pbls" }
```
- `filetypes` :
```lua
{ "proto" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pbls.lua:4](../lua/lspconfig/configs/pbls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## perlls
https://github.com/richterger/Perl-LanguageServer/tree/master/clients/vscode/perl
`Perl-LanguageServer`, a language server for Perl.
To use the language server, ensure that you have Perl::LanguageServer installed and perl command is on your path.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.perlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "perl", "-MPerl::LanguageServer", "-e", "Perl::LanguageServer::run", "--", "--port 13603", "--nostdio 0" }
```
- `filetypes` :
```lua
{ "perl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/perlls.lua:2](../lua/lspconfig/configs/perlls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
perl = {
fileFilter = { ".pm", ".pl" },
ignoreDirs = ".git",
perlCmd = "perl",
perlInc = " "
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## perlnavigator
https://github.com/bscan/PerlNavigator
A Perl language server. It can be installed via npm:
```sh
npm i -g perlnavigator-server
```
At minimum, you will need `perl` in your path. If you want to use a non-standard `perl` you will need to set your configuration like so:
```lua
settings = {
perlnavigator = {
perlPath = '/some/odd/location/my-perl'
}
}
```
The `contributes.configuration.properties` section of `perlnavigator`'s `package.json` has all available configuration settings. All
settings have a reasonable default, but, at minimum, you may want to point `perlnavigator` at your `perltidy` and `perlcritic` configurations.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.perlnavigator.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "perlnavigator" }
```
- `filetypes` :
```lua
{ "perl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/perlnavigator.lua:2](../lua/lspconfig/configs/perlnavigator.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## perlpls
https://github.com/FractalBoy/perl-language-server
https://metacpan.org/pod/PLS
`PLS`, another language server for Perl.
To use the language server, ensure that you have PLS installed and that it is in your path
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.perlpls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pls" }
```
- `filetypes` :
```lua
{ "perl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/perlpls.lua:2](../lua/lspconfig/configs/perlpls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
perl = {
perlcritic = {
enabled = false
},
syntax = {
enabled = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pest_ls
https://github.com/pest-parser/pest-ide-tools
Language server for pest grammars.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pest_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pest-language-server" }
```
- `filetypes` :
```lua
{ "pest" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pest_ls.lua:2](../lua/lspconfig/configs/pest_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## phan
https://github.com/phan/phan
Installation: https://github.com/phan/phan#getting-started
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.phan.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "phan", "-m", "json", "--no-color", "--no-progress-bar", "-x", "-u", "-S", "--language-server-on-stdin", "--allow-polyfill-parser" }
```
- `filetypes` :
```lua
{ "php" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/phan.lua:17](../lua/lspconfig/configs/phan.lua#L17)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## phpactor
https://github.com/phpactor/phpactor
Installation: https://phpactor.readthedocs.io/en/master/usage/standalone.html#global-installation
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.phpactor.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "phpactor", "language-server" }
```
- `filetypes` :
```lua
{ "php" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/phpactor.lua:4](../lua/lspconfig/configs/phpactor.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pico8_ls
https://github.com/japhib/pico8-ls
Full language support for the PICO-8 dialect of Lua.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pico8_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pico8-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "p8" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pico8_ls.lua:4](../lua/lspconfig/configs/pico8_ls.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pkgbuild_language_server
https://github.com/Freed-Wu/pkgbuild-language-server
Language server for ArchLinux/Windows Msys2's PKGBUILD.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pkgbuild_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pkgbuild-language-server" }
```
- `filetypes` :
```lua
{ "PKGBUILD" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pkgbuild_language_server.lua:2](../lua/lspconfig/configs/pkgbuild_language_server.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## please
https://github.com/thought-machine/please
High-performance extensible build system for reproducible multi-language builds.
The `plz` binary will automatically install the LSP for you on first run
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.please.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "plz", "tool", "lps" }
```
- `filetypes` :
```lua
{ "bzl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/please.lua:4](../lua/lspconfig/configs/please.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-12 05:26:19 +00:00
## poryscript_pls
https://github.com/huderlem/poryscript-pls
Language server for poryscript (a high level scripting language for GBA-era Pokémon decompilation projects)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-12 05:26:19 +00:00
```lua
require'lspconfig'.poryscript_pls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "poryscript-pls" }
```
- `filetypes` :
```lua
{ "pory" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/poryscript_pls.lua:2](../lua/lspconfig/configs/poryscript_pls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-12 05:26:19 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## postgres_lsp
https://github.com/supabase/postgres_lsp
A Language Server for Postgres
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.postgres_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "postgres_lsp" }
```
- `filetypes` :
```lua
{ "sql" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/postgres_lsp.lua:4](../lua/lspconfig/configs/postgres_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## powershell_es
https://github.com/PowerShell/PowerShellEditorServices
Language server for PowerShell.
To install, download and extract PowerShellEditorServices.zip
from the [releases](https://github.com/PowerShell/PowerShellEditorServices/releases).
To configure the language server, set the property `bundle_path` to the root
of the extracted PowerShellEditorServices.zip.
The default configuration doesn't set `cmd` unless `bundle_path` is specified.
```lua
require'lspconfig'.powershell_es.setup{
bundle_path = 'c:/w/PowerShellEditorServices',
}
```
By default the languageserver is started in `pwsh` (PowerShell Core). This can be changed by specifying `shell`.
```lua
require'lspconfig'.powershell_es.setup{
bundle_path = 'c:/w/PowerShellEditorServices',
shell = 'powershell.exe',
}
```
Note that the execution policy needs to be set to `Unrestricted` for the languageserver run under PowerShell
If necessary, specific `cmd` can be defined instead of `bundle_path`.
See [PowerShellEditorServices](https://github.com/PowerShell/PowerShellEditorServices#stdio)
to learn more.
```lua
require'lspconfig'.powershell_es.setup{
cmd = {'pwsh', '-NoLogo', '-NoProfile', '-Command', "c:/PSES/Start-EditorServices.ps1 ..."}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.powershell_es.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "ps1" }
```
docs: update configs.md skip-checks: true
2025-01-05 14:47:47 +00:00
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/powershell_es.lua:14](../lua/lspconfig/configs/powershell_es.lua#L14)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/powershell_es.lua:14](../lua/lspconfig/configs/powershell_es.lua#L14)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `shell` :
```lua
"pwsh"
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## prismals
Language Server for the Prisma JavaScript and TypeScript ORM
`@prisma/language-server` can be installed via npm
```sh
npm install -g @prisma/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.prismals.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "prisma-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "prisma" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/prismals.lua:4](../lua/lspconfig/configs/prismals.lua#L4)
- `settings` :
```lua
{
prisma = {
prismaFmtBinPath = ""
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## prolog_ls
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/jamesnvc/lsp_server
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
Language Server Protocol server for SWI-Prolog
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.prolog_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "swipl", "-g", "use_module(library(lsp_server)).", "-g", "lsp_server:main", "-t", "halt", "--", "stdio" }
```
- `filetypes` :
```lua
{ "prolog" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/prolog_ls.lua:4](../lua/lspconfig/configs/prolog_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## prosemd_lsp
https://github.com/kitten/prosemd-lsp
An experimental LSP for Markdown.
Please see the manual installation instructions: https://github.com/kitten/prosemd-lsp#manual-installation
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.prosemd_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "prosemd-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "markdown" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/prosemd_lsp.lua:2](../lua/lspconfig/configs/prosemd_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## protols
https://github.com/coder3101/protols
`protols` can be installed via `cargo`:
```sh
cargo install protols
```
A Language Server for proto3 files. It uses tree-sitter and runs in single file mode.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.protols.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "protols" }
```
- `filetypes` :
```lua
{ "proto" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/protols.lua:2](../lua/lspconfig/configs/protols.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## psalm
https://github.com/vimeo/psalm
Can be installed with composer.
```sh
composer global require vimeo/psalm
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.psalm.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "psalm", "--language-server" }
```
- `filetypes` :
```lua
{ "php" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/psalm.lua:4](../lua/lspconfig/configs/psalm.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pug
https://github.com/opa-oz/pug-lsp
An implementation of the Language Protocol Server for [Pug.js](http://pugjs.org)
PugLSP can be installed via `go get github.com/opa-oz/pug-lsp`, or manually downloaded from [releases page](https://github.com/opa-oz/pug-lsp/releases)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pug.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pug-lsp" }
```
- `filetypes` :
```lua
{ "pug" }
```
docs: update configs.md skip-checks: true
2024-12-13 13:32:03 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pug.lua:2](../lua/lspconfig/configs/pug.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## puppet
LSP server for Puppet.
Installation:
- Clone the editor-services repository:
https://github.com/puppetlabs/puppet-editor-services
- Navigate into that directory and run: `bundle install`
- Install the 'puppet-lint' gem: `gem install puppet-lint`
- Add that repository to $PATH.
- Ensure you can run `puppet-languageserver` from outside the editor-services directory.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.puppet.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "puppet-languageserver", "--stdio" }
```
- `filetypes` :
```lua
{ "puppet" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/puppet.lua:11](../lua/lspconfig/configs/puppet.lua#L11)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## purescriptls
https://github.com/nwolverson/purescript-language-server
The `purescript-language-server` can be added to your project and `$PATH` via
* JavaScript package manager such as npm, pnpm, Yarn, et al.
* Nix under the `nodePackages` and `nodePackages_latest` package sets
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.purescriptls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "purescript-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "purescript" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/purescriptls.lua:4](../lua/lspconfig/configs/purescriptls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pylsp
https://github.com/python-lsp/python-lsp-server
A Python 3.6+ implementation of the Language Server Protocol.
See the [project's README](https://github.com/python-lsp/python-lsp-server) for installation instructions.
Configuration options are documented [here](https://github.com/python-lsp/python-lsp-server/blob/develop/CONFIGURATION.md).
In order to configure an option, it must be translated to a nested Lua table and included in the `settings` argument to the `setup{}` function.
For example, in order to set the `pylsp.plugins.pycodestyle.ignore` option:
```lua
require'lspconfig'.pylsp.setup{
settings = {
pylsp = {
plugins = {
pycodestyle = {
ignore = {'W391'},
maxLineLength = 100
}
}
}
}
}
```
Note: This is a community fork of `pyls`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pylsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pylsp" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pylsp.lua:4](../lua/lspconfig/configs/pylsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pylyzer
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/mtshiba/pylyzer
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
`pylyzer`, a fast static code analyzer & language server for Python.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pylyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pylyzer", "--server" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pylyzer.lua:4](../lua/lspconfig/configs/pylyzer.lua#L4)
- `settings` :
```lua
{
python = {
checkOnType = false,
diagnostics = true,
inlayHints = true,
smartCompletion = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pyre
https://pyre-check.org/
`pyre` a static type checker for Python 3.
`pyre` offers an extremely limited featureset. It currently only supports diagnostics,
which are triggered on save.
Do not report issues for missing features in `pyre` to `lspconfig`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pyre.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pyre", "persistent" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pyre.lua:4](../lua/lspconfig/configs/pyre.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## pyright
https://github.com/microsoft/pyright
`pyright`, a static type checker and language server for python
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.pyright.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- PyrightOrganizeImports: Organize Imports
- PyrightSetPythonPath: Reconfigure pyright with the provided python path
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "pyright-langserver", "--stdio" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/pyright.lua:44](../lua/lspconfig/configs/pyright.lua#L44)
- `settings` :
```lua
{
python = {
analysis = {
autoSearchPaths = true,
diagnosticMode = "openFilesOnly",
useLibraryCodeForTypes = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## qml_lsp
https://invent.kde.org/sdk/qml-lsp
LSP implementation for QML (autocompletion, live linting, etc. in editors)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.qml_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "qml-lsp" }
```
- `filetypes` :
```lua
{ "qmljs" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/qml_lsp.lua:4](../lua/lspconfig/configs/qml_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## qmlls
https://github.com/qt/qtdeclarative
LSP implementation for QML (autocompletion, live linting, etc. in editors),
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.qmlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "qmlls" }
```
- `filetypes` :
```lua
{ "qml", "qmljs" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/qmlls.lua:2](../lua/lspconfig/configs/qmlls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## quick_lint_js
https://quick-lint-js.com/
quick-lint-js finds bugs in JavaScript programs.
See installation [instructions](https://quick-lint-js.com/install/)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.quick_lint_js.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "quick-lint-js", "--lsp-server" }
```
- `filetypes` :
```lua
{ "javascript", "typescript" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/quick_lint_js.lua:4](../lua/lspconfig/configs/quick_lint_js.lua#L4)
- `single_file_support` : `true`
regen docs
2024-10-24 15:06:10 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## r_language_server
[languageserver](https://github.com/REditorSupport/languageserver) is an
implementation of the Microsoft's Language Server Protocol for the R
language.
It is released on CRAN and can be easily installed by
```r
install.packages("languageserver")
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.r_language_server.setup{}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
Default config:
- `cmd` :
```lua
{ "R", "--no-echo", "-e", "languageserver::run()" }
```
- `filetypes` :
```lua
{ "r", "rmd" }
```
- `log_level` :
```lua
2
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/r_language_server.lua:2](../lua/lspconfig/configs/r_language_server.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## racket_langserver
[https://github.com/jeapostrophe/racket-langserver](https://github.com/jeapostrophe/racket-langserver)
The Racket language server. This project seeks to use
[DrRacket](https://github.com/racket/drracket)'s public API to provide
functionality that mimics DrRacket's code tools as closely as possible.
Install via `raco`: `raco pkg install racket-langserver`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.racket_langserver.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "racket", "--lib", "racket-langserver" }
```
- `filetypes` :
```lua
{ "racket", "scheme" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/racket_langserver.lua:2](../lua/lspconfig/configs/racket_langserver.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## raku_navigator
https://github.com/bscan/RakuNavigator
A Raku language server
**By default, raku_navigator doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path.
You have to install the language server manually.
Clone the RakuNavigator repo, install based on the [instructions](https://github.com/bscan/raku_Navigator#installation-for-other-editors),
and point `cmd` to `server.js` inside the `server/out` directory:
```lua
cmd = {'node', '<path_to_repo>/server/out/server.js', '--stdio'}
```
At minimum, you will need `raku` in your path. If you want to use a non-standard `raku` you will need to set your configuration like so:
```lua
settings = {
raku_navigator = {
rakuPath = '/some/odd/location/my-raku'
}
}
```
The `contributes.configuration.properties` section of `raku_navigator`'s `package.json` has all available configuration settings. All
settings have a reasonable default, but, at minimum, you may want to point `raku_navigator` at your `raku_tidy` and `raku_critic` configurations.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.raku_navigator.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{}
```
- `filetypes` :
```lua
{ "raku" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/raku_navigator.lua:2](../lua/lspconfig/configs/raku_navigator.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## reason_ls
Reason language server
You can install reason language server from [reason-language-server](https://github.com/jaredly/reason-language-server) repository.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.reason_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "reason-language-server" }
```
- `filetypes` :
```lua
{ "reason" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/reason_ls.lua:4](../lua/lspconfig/configs/reason_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## regal
https://github.com/StyraInc/regal
A linter for Rego, with support for running as an LSP server.
`regal` can be installed by running:
```sh
go install github.com/StyraInc/regal@latest
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.regal.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "regal", "language-server" }
```
- `filetypes` :
```lua
{ "rego" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/regal.lua:4](../lua/lspconfig/configs/regal.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## regols
https://github.com/kitagry/regols
OPA Rego language server.
`regols` can be installed by running:
```sh
go install github.com/kitagry/regols@latest
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.regols.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "regols" }
```
- `filetypes` :
```lua
{ "rego" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/regols.lua:4](../lua/lspconfig/configs/regols.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## relay_lsp
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/facebook/relay
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
`Relay` is a JavaScript framework for building data-driven React applications
Setup:
- Make sure you have a Relay config file somewhere in your project.
- We support standard config file formats (`.yml`, `.js`, `.json`), and the the `relay` field in your `package.json`
- Make sure you have the `relay-compiler` installed in your project. The bare minimum is v13.
- Make sure you are able to run the `relay-compiler` command from the command line. If `yarn relay-compiler` works, it's very likely that the LSP will work.
- Remove / disable any conflicting GraphQL LSPs you have installed.
Relay LSP is a part of the Relay Compiler binary and available when adding `relay-compiler` to your project's devDependencies.
```lua
require'lspconfig'.relay_lsp.setup {
-- (default: false) Whether or not we should automatically start
-- the Relay Compiler in watch mode when you open a project
auto_start_compiler = false,
-- (default: null) Path to a relay config relative to the
-- `root_dir`. Without this, the compiler will search for your
-- config. This is helpful if your relay project is in a nested
-- directory.
path_to_config = nil,
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.relay_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `auto_start_compiler` : `false`
- `cmd` :
```lua
{ "relay-compiler", "lsp" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
```
- `handlers` :
```lua
{
["window/showStatus"] = <function 1>
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/relay_lsp.lua:5](../lua/lspconfig/configs/relay_lsp.lua#L5)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/relay_lsp.lua:5](../lua/lspconfig/configs/relay_lsp.lua#L5)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## remark_ls
https://github.com/remarkjs/remark-language-server
`remark-language-server` can be installed via `npm`:
```sh
npm install -g remark-language-server
```
`remark-language-server` uses the same
[configuration files](https://github.com/remarkjs/remark/tree/main/packages/remark-cli#example-config-files-json-yaml-js)
as `remark-cli`.
This uses a plugin based system. Each plugin needs to be installed locally using `npm` or `yarn`.
For example, given the following `.remarkrc.json`:
```json
{
"presets": [
"remark-preset-lint-recommended"
]
}
```
`remark-preset-lint-recommended` needs to be installed in the local project:
```sh
npm install remark-preset-lint-recommended
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.remark_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "remark-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "markdown" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/remark_ls.lua:4](../lua/lspconfig/configs/remark_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rescriptls
https://github.com/rescript-lang/rescript-vscode/tree/master/server
ReScript Language Server can be installed via npm:
```sh
npm install -g @rescript/language-server
```
See [package.json](https://github.com/rescript-lang/rescript-vscode/blob/master/package.json#L139)
for init_options supported.
For example, in order to disable the `inlayHints` option:
```lua
require'lspconfig'.pylsp.setup{
settings = {
rescript = {
settings = {
inlayHints = { enable = false },
},
},
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rescriptls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rescript-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "rescript" }
```
- `init_options` :
```lua
{
extensionConfiguration = {
allowBuiltInFormatter = true,
askToStartBuild = false,
cache = {
projectConfig = {
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
enabled = true
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
},
codeLens = true,
incrementalTypechecking = {
acrossFiles = true,
enabled = true
},
inlayHints = {
enable = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rescriptls.lua:4](../lua/lspconfig/configs/rescriptls.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rls
https://github.com/rust-lang/rls
rls, a language server for Rust
See https://github.com/rust-lang/rls#setup to setup rls itself.
See https://github.com/rust-lang/rls#configuration for rls-specific settings.
All settings listed on the rls configuration section of the readme
must be set under settings.rust as follows:
```lua
nvim_lsp.rls.setup {
settings = {
rust = {
unstable_features = true,
build_on_save = false,
all_features = true,
},
},
}
```
If you want to use rls for a particular build, eg nightly, set cmd as follows:
```lua
cmd = {"rustup", "run", "nightly", "rls"}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rls" }
```
- `filetypes` :
```lua
{ "rust" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rls.lua:4](../lua/lspconfig/configs/rls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rnix
https://github.com/nix-community/rnix-lsp
A language server for Nix providing basic completion and formatting via nixpkgs-fmt.
To install manually, run `cargo install rnix-lsp`. If you are using nix, rnix-lsp is in nixpkgs.
This server accepts configuration via the `settings` key.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rnix.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rnix-lsp" }
```
- `filetypes` :
```lua
{ "nix" }
```
- `init_options` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rnix.lua:2](../lua/lspconfig/configs/rnix.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-11-12 08:46:09 +00:00
## robotcode
https://robotcode.io
RobotCode - Language Server Protocol implementation for Robot Framework.
Snippet to enable the language server:
```lua
require'lspconfig'.robotcode.setup{}
```
Default config:
- `cmd` :
```lua
{ "robotcode", "language-server" }
```
- `filetypes` :
```lua
{ "robot", "resource" }
```
- `get_language_id` source (use "gF" to visit): [../lua/lspconfig/configs/robotcode.lua:4](../lua/lspconfig/configs/robotcode.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/robotcode.lua:4](../lua/lspconfig/configs/robotcode.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## robotframework_ls
https://github.com/robocorp/robotframework-lsp
Language Server Protocol implementation for Robot Framework.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.robotframework_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "robotframework_ls" }
```
- `filetypes` :
```lua
{ "robot" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/robotframework_ls.lua:4](../lua/lspconfig/configs/robotframework_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## roc_ls
https://github.com/roc-lang/roc/tree/main/crates/language_server#roc_language_server
The built-in language server for the Roc programming language.
[Installation](https://github.com/roc-lang/roc/tree/main/crates/language_server#installing)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.roc_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "roc_language_server" }
```
- `filetypes` :
```lua
{ "roc" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/roc_ls.lua:2](../lua/lspconfig/configs/roc_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rome
https://rome.tools
Language server for the Rome Frontend Toolchain.
(Unmaintained, use [Biome](https://biomejs.dev/blog/annoucing-biome) instead.)
```sh
npm install [-g] rome
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rome.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rome", "lsp-proxy" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "json", "typescript", "typescript.tsx", "typescriptreact" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rome.lua:2](../lua/lspconfig/configs/rome.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rubocop
https://github.com/rubocop/rubocop
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rubocop.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rubocop", "--lsp" }
```
- `filetypes` :
```lua
{ "ruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rubocop.lua:4](../lua/lspconfig/configs/rubocop.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ruby_lsp
https://shopify.github.io/ruby-lsp/
This gem is an implementation of the language server protocol specification for
Ruby, used to improve editor features.
Install the gem. There's no need to require it, since the server is used as a
standalone executable.
```sh
docs: update configs.md skip-checks: true
2025-01-03 08:35:45 +00:00
gem install ruby-lsp
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ruby_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ruby-lsp" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-11-15 05:47:45 +00:00
{ "ruby", "eruby" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `init_options` :
```lua
{
formatter = "auto"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ruby_lsp.lua:4](../lua/lspconfig/configs/ruby_lsp.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ruff
https://github.com/astral-sh/ruff
A Language Server Protocol implementation for Ruff, an extremely fast Python linter and code formatter, written in Rust. It can be installed via `pip`.
```sh
pip install ruff
```
**Available in Ruff `v0.4.5` in beta and stabilized in Ruff `v0.5.3`.**
This is the new built-in language server written in Rust. It supports the same feature set as `ruff-lsp`, but with superior performance and no installation required. Note that the `ruff-lsp` server will continue to be maintained until further notice.
Server settings can be provided via:
```lua
require('lspconfig').ruff.setup({
init_options = {
settings = {
-- Server settings should go here
}
}
})
```
Refer to the [documentation](https://docs.astral.sh/ruff/editors/) for more details.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ruff.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ruff", "server" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ruff.lua:4](../lua/lspconfig/configs/ruff.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ruff_lsp
https://github.com/astral-sh/ruff-lsp
A Language Server Protocol implementation for Ruff, an extremely fast Python linter and code transformation tool, written in Rust. It can be installed via pip.
```sh
pip install ruff-lsp
```
Extra CLI arguments for `ruff` can be provided via
```lua
require'lspconfig'.ruff_lsp.setup{
init_options = {
settings = {
-- Any extra CLI arguments for `ruff` go here.
args = {},
}
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ruff_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ruff-lsp" }
```
- `filetypes` :
```lua
{ "python" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ruff_lsp.lua:4](../lua/lspconfig/configs/ruff_lsp.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rune_languageserver
https://crates.io/crates/rune-languageserver
A language server for the [Rune](https://rune-rs.github.io/) Language,
an embeddable dynamic programming language for Rust
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rune_languageserver.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "rune-languageserver" }
```
- `filetypes` :
```lua
{ "rune" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rune_languageserver.lua:2](../lua/lspconfig/configs/rune_languageserver.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## rust_analyzer
https://github.com/rust-lang/rust-analyzer
rust-analyzer (aka rls 2.0), a language server for Rust
See [docs](https://github.com/rust-lang/rust-analyzer/blob/master/docs/user/generated_config.adoc) for extra settings. The settings can be used like this:
```lua
require'lspconfig'.rust_analyzer.setup{
settings = {
['rust-analyzer'] = {
diagnostics = {
enable = false;
}
}
}
}
```
Note: do not set `init_options` for this LS config, it will be automatically populated by the contents of settings["rust-analyzer"] per
https://github.com/rust-lang/rust-analyzer/blob/eb5da56d839ae0a9e9f50774fa3eb78eb0964550/docs/dev/lsp-extensions.md?plain=1#L26.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.rust_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- CargoReload: Reload current cargo workspace
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `before_init` source (use "gF" to visit): [../lua/lspconfig/configs/rust_analyzer.lua:36](../lua/lspconfig/configs/rust_analyzer.lua#L36)
- `capabilities` :
```lua
{
experimental = {
serverStatusNotification = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `cmd` :
```lua
{ "rust-analyzer" }
```
- `filetypes` :
```lua
{ "rust" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/rust_analyzer.lua:36](../lua/lspconfig/configs/rust_analyzer.lua#L36)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## salt_ls
Language server for Salt configuration files.
https://github.com/dcermak/salt-lsp
The language server can be installed with `pip`:
```sh
pip install salt-lsp
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.salt_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "salt_lsp_server" }
```
- `filetypes` :
```lua
{ "sls" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/salt_ls.lua:2](../lua/lspconfig/configs/salt_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## scheme_langserver
https://github.com/ufo5260987423/scheme-langserver
`scheme-langserver`, a language server protocol implementation for scheme.
And for nvim user, please add .sls to scheme file extension list.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.scheme_langserver.setup{}
regen docs
2024-10-24 15:06:10 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "scheme-langserver", "~/.scheme-langserver.log", "enable", "disable" }
```
- `filetypes` :
```lua
{ "scheme" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/scheme_langserver.lua:9](../lua/lspconfig/configs/scheme_langserver.lua#L9)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## scry
https://github.com/crystal-lang-tools/scry
Crystal language server.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.scry.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "scry" }
```
- `filetypes` :
```lua
{ "crystal" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/scry.lua:4](../lua/lspconfig/configs/scry.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2025-01-13 07:41:33 +00:00
## selene3p_ls
https://github.com/antonk52/lua-3p-language-servers
3rd party Language Server for Selene lua linter
Snippet to enable the language server:
```lua
require'lspconfig'.selene3p_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "selene-3p-language-server" }
```
- `filetypes` :
```lua
{ "lua" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/selene3p_ls.lua:4](../lua/lspconfig/configs/selene3p_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## serve_d
regen docs
2024-10-24 15:06:10 +00:00
https://github.com/Pure-D/serve-d
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
`Microsoft language server protocol implementation for D using workspace-d.`
Download a binary from https://github.com/Pure-D/serve-d/releases and put it in your $PATH.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.serve_d.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "serve-d" }
```
- `filetypes` :
```lua
{ "d" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/serve_d.lua:4](../lua/lspconfig/configs/serve_d.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## shopify_theme_ls
https://shopify.dev/docs/api/shopify-cli
[Language Server](https://shopify.dev/docs/themes/tools/cli/language-server) and Theme Check (linter) for Shopify themes.
`shopify` can be installed via npm `npm install -g @shopify/cli`.
Note: This LSP already includes Theme Check so you don't need to use the `theme_check` server configuration as well.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.shopify_theme_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "shopify", "theme", "language-server" }
```
- `filetypes` :
```lua
{ "liquid" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/shopify_theme_ls.lua:11](../lua/lspconfig/configs/shopify_theme_ls.lua#L11)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sixtyfps
https://github.com/sixtyfpsui/sixtyfps
`SixtyFPS`'s language server
You can build and install `sixtyfps-lsp` binary with `cargo`:
```sh
cargo install sixtyfps-lsp
```
Vim does not have built-in syntax for the `sixtyfps` filetype currently.
This can be added via an autocmd:
```lua
vim.cmd [[ autocmd BufRead,BufNewFile *.60 set filetype=sixtyfps ]]
```
or by installing a filetype plugin such as https://github.com/RustemB/sixtyfps-vim
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sixtyfps.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "sixtyfps-lsp" }
```
- `filetypes` :
```lua
{ "sixtyfps" }
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## slangd
https://github.com/shader-slang/slang
The `slangd` binary can be downloaded as part of [slang releases](https://github.com/shader-slang/slang/releases) or
by [building `slang` from source](https://github.com/shader-slang/slang/blob/master/docs/building.md).
The server can be configured by passing a "settings" object to `slangd.setup{}`:
```lua
require('lspconfig').slangd.setup{
settings = {
slang = {
predefinedMacros = {"MY_VALUE_MACRO=1"},
inlayHints = {
deducedTypes = true,
parameterNames = true,
}
}
}
}
```
Available options are documented [here](https://github.com/shader-slang/slang-vscode-extension/tree/main?tab=readme-ov-file#configurations)
or in more detail [here](https://github.com/shader-slang/slang-vscode-extension/blob/main/package.json#L70).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.slangd.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "slangd" }
```
- `filetypes` :
```lua
{ "hlsl", "shaderslang" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/slangd.lua:8](../lua/lspconfig/configs/slangd.lua#L8)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## slint_lsp
https://github.com/slint-ui/slint
`Slint`'s language server
You can build and install `slint-lsp` binary with `cargo`:
```sh
cargo install slint-lsp
```
Vim does not have built-in syntax for the `slint` filetype at this time.
This can be added via an autocmd:
```lua
vim.cmd [[ autocmd BufRead,BufNewFile *.slint set filetype=slint ]]
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.slint_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "slint-lsp" }
```
- `filetypes` :
```lua
{ "slint" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/slint_lsp.lua:2](../lua/lspconfig/configs/slint_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## smarty_ls
https://github.com/landeaux/vscode-smarty-langserver-extracted
Language server for Smarty.
`smarty-language-server` can be installed via `npm`:
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```sh
npm i -g vscode-smarty-langserver-extracted
```
Snippet to enable the language server:
```lua
require'lspconfig'.smarty_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "smarty-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "smarty" }
```
- `init_options` :
```lua
{}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/smarty_ls.lua:4](../lua/lspconfig/configs/smarty_ls.lua#L4)
- `settings` :
```lua
{
css = {
validate = true
},
smarty = {
pluginDirs = {}
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## smithy_ls
https://github.com/awslabs/smithy-language-server
`Smithy Language Server`, A Language Server Protocol implementation for the Smithy IDL
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.smithy_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "smithy-language-server", "0" }
```
- `filetypes` :
```lua
{ "smithy" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/smithy_ls.lua:7](../lua/lspconfig/configs/smithy_ls.lua#L7)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## snakeskin_ls
https://www.npmjs.com/package/@snakeskin/cli
`snakeskin cli` can be installed via `npm`:
```sh
npm install -g @snakeskin/cli
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.snakeskin_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "snakeskin-cli", "lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "ss" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/snakeskin_ls.lua:4](../lua/lspconfig/configs/snakeskin_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## snyk_ls
https://github.com/snyk/snyk-ls
LSP for Snyk Open Source, Snyk Infrastructure as Code, and Snyk Code.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.snyk_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "snyk-ls" }
```
- `filetypes` :
```lua
{ "go", "gomod", "javascript", "typescript", "json", "python", "requirements", "helm", "yaml", "terraform", "terraform-vars" }
```
- `init_options` :
```lua
{
activateSnykCode = "true"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/snyk_ls.lua:4](../lua/lspconfig/configs/snyk_ls.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solang
A language server for Solidity
See the [documentation](https://solang.readthedocs.io/en/latest/installing.html) for installation instructions.
The language server only provides the following capabilities:
* Syntax highlighting
* Diagnostics
* Hover
There is currently no support for completion, goto definition, references, or other functionality.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solang.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "solang", "language-server", "--target", "evm" }
```
- `filetypes` :
```lua
{ "solidity" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solang.lua:2](../lua/lspconfig/configs/solang.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solargraph
https://solargraph.org/
solargraph, a language server for Ruby
You can install solargraph via gem install.
```sh
gem install --user-install solargraph
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solargraph.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "solargraph", "stdio" }
```
- `filetypes` :
```lua
{ "ruby" }
```
- `init_options` :
```lua
{
formatting = true
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solargraph.lua:4](../lua/lspconfig/configs/solargraph.lua#L4)
- `settings` :
```lua
{
solargraph = {
diagnostics = true
regen docs
2024-10-24 15:06:10 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solc
https://docs.soliditylang.org/en/latest/installing-solidity.html
solc is the native language server for the Solidity language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solc.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "solc", "--lsp" }
```
- `filetypes` :
```lua
{ "solidity" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solc.lua:4](../lua/lspconfig/configs/solc.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solidity
https://github.com/qiuxiang/solidity-ls
npm i solidity-ls -g
Make sure that solc is installed and it's the same version of the file. solc-select is recommended.
Solidity language server is a LSP with autocomplete, go to definition and diagnostics.
If you use brownie, use this root_dir:
root_dir = util.root_pattern('brownie-config.yaml', '.git')
on includePath, you can add an extra path to search for external libs, on remapping you can remap lib <> path, like:
```lua
{ solidity = { includePath = '/Users/your_user/.brownie/packages/', remapping = { ["@OpenZeppelin/"] = 'OpenZeppelin/openzeppelin-contracts@4.6.0/' } } }
```
**For brownie users**
Change the root_dir to:
```lua
root_pattern("brownie-config.yaml", ".git")
```
The best way of using it is to have a package.json in your project folder with the packages that you will use.
After installing with package.json, just create a `remappings.txt` with:
```
@OpenZeppelin/=node_modules/OpenZeppelin/openzeppelin-contracts@4.6.0/
```
You can omit the node_modules as well.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solidity.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "solidity-ls", "--stdio" }
```
- `filetypes` :
```lua
{ "solidity" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solidity.lua:4](../lua/lspconfig/configs/solidity.lua#L4)
- `settings` :
```lua
{
solidity = {
includePath = "",
remapping = {}
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solidity_ls
https://github.com/juanfranblanco/vscode-solidity
`vscode-solidity-server` can be installed via `npm`:
```sh
npm install -g vscode-solidity-server
```
`vscode-solidity-server` is a language server for the Solidity language ported from the VSCode "solidity" extension.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solidity_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscode-solidity-server", "--stdio" }
```
- `filetypes` :
```lua
{ "solidity" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solidity_ls.lua:14](../lua/lspconfig/configs/solidity_ls.lua#L14)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## solidity_ls_nomicfoundation
https://github.com/NomicFoundation/hardhat-vscode/blob/development/server/README.md
`nomicfoundation-solidity-language-server` can be installed via `npm`:
```sh
npm install -g @nomicfoundation/solidity-language-server
```
A language server for the Solidity programming language, built by the Nomic Foundation for the Ethereum community.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.solidity_ls_nomicfoundation.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nomicfoundation-solidity-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "solidity" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/solidity_ls_nomicfoundation.lua:14](../lua/lspconfig/configs/solidity_ls_nomicfoundation.lua#L14)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## somesass_ls
https://github.com/wkillerud/some-sass/tree/main/packages/language-server
`some-sass-language-server` can be installed via `npm`:
```sh
npm i -g some-sass-language-server
```
The language server provides:
- Full support for @use and @forward, including aliases, prefixes and hiding.
- Workspace-wide code navigation and refactoring, such as Rename Symbol.
- Rich documentation through SassDoc.
- Language features for %placeholder-selectors, both when using them and writing them.
- Suggestions and hover info for built-in Sass modules, when used with @use.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.somesass_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "some-sass-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "scss", "sass" }
```
- `name` :
```lua
"somesass_ls"
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/somesass_ls.lua:4](../lua/lspconfig/configs/somesass_ls.lua#L4)
- `settings` :
```lua
{
somesass = {
suggestAllFromOpenDocument = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sorbet
https://sorbet.org
Sorbet is a fast, powerful type checker designed for Ruby.
You can install Sorbet via gem install. You might also be interested in how to set
Sorbet up for new projects: https://sorbet.org/docs/adopting.
```sh
gem install sorbet
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sorbet.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "srb", "tc", "--lsp" }
```
- `filetypes` :
```lua
{ "ruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/sorbet.lua:4](../lua/lspconfig/configs/sorbet.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sourcekit
https://github.com/apple/sourcekit-lsp
Language server for Swift and C/C++/Objective-C.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sourcekit.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "sourcekit-lsp" }
```
- `filetypes` :
```lua
{ "swift", "objc", "objcpp", "c", "cpp" }
```
- `get_language_id` source (use "gF" to visit): [../lua/lspconfig/configs/sourcekit.lua:4](../lua/lspconfig/configs/sourcekit.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/sourcekit.lua:4](../lua/lspconfig/configs/sourcekit.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sourcery
https://github.com/sourcery-ai/sourcery
Refactor Python instantly using the power of AI.
It requires the init_options param to be populated as shown below and will respond with the list of ServerCapabilities that it supports:
```lua
require'lspconfig'.sourcery.setup {
init_options = {
--- The Sourcery token for authenticating the user.
--- This is retrieved from the Sourcery website and must be
--- provided by each user. The extension must provide a
--- configuration option for the user to provide this value.
token = <YOUR_TOKEN>,
--- The extension's name and version as defined by the extension.
extension_version = 'vim.lsp',
--- The editor's name and version as defined by the editor.
editor_version = 'vim',
},
}
```
Alternatively, you can login to sourcery by running `sourcery login` with sourcery-cli.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sourcery.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "sourcery", "lsp" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "python", "typescript", "typescriptreact" }
```
- `init_options` :
```lua
{
editor_version = "vim",
extension_version = "vim.lsp"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/sourcery.lua:32](../lua/lspconfig/configs/sourcery.lua#L32)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## spectral
https://github.com/luizcorreia/spectral-language-server
`A flexible JSON/YAML linter for creating automated style guides, with baked in support for OpenAPI v2 & v3.`
`spectral-language-server` can be installed via `npm`:
```sh
npm i -g spectral-language-server
```
See [vscode-spectral](https://github.com/stoplightio/vscode-spectral#extension-settings) for configuration options.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.spectral.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "spectral-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "yaml", "json", "yml" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/spectral.lua:6](../lua/lspconfig/configs/spectral.lua#L6)
- `settings` :
```lua
{
enable = true,
run = "onType",
validateLanguages = { "yaml", "json", "yml" }
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## spyglassmc_language_server
https://github.com/SpyglassMC/Spyglass/tree/main/packages/language-server
Language server for Minecraft datapacks.
`spyglassmc-language-server` can be installed via `npm`:
```sh
npm i -g @spyglassmc/language-server
```
You may also need to configure the filetype:
`autocmd BufNewFile,BufRead *.mcfunction set filetype=mcfunction`
This is automatically done by [CrystalAlpha358/vim-mcfunction](https://github.com/CrystalAlpha358/vim-mcfunction), which also provide syntax highlight.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.spyglassmc_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "spyglassmc-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "mcfunction" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/spyglassmc_language_server.lua:4](../lua/lspconfig/configs/spyglassmc_language_server.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sqlls
https://github.com/joe-re/sql-language-server
This LSP can be installed via `npm`. Find further instructions on manual installation of the sql-language-server at [joe-re/sql-language-server](https://github.com/joe-re/sql-language-server).
<br>
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sqlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "sql-language-server", "up", "--method", "stdio" }
```
- `filetypes` :
```lua
{ "sql", "mysql" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/sqlls.lua:4](../lua/lspconfig/configs/sqlls.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## sqls
https://github.com/sqls-server/sqls
```lua
require'lspconfig'.sqls.setup{
cmd = {"path/to/command", "-config", "path/to/config.yml"};
...
}
```
Sqls can be installed via `go get github.com/sqls-server/sqls`. Instructions for compiling Sqls from the source can be found at [sqls-server/sqls](https://github.com/sqls-server/sqls).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.sqls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "sqls" }
```
- `filetypes` :
```lua
{ "sql", "mysql" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/sqls.lua:4](../lua/lspconfig/configs/sqls.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## standardrb
https://github.com/testdouble/standard
Ruby Style Guide, with linter & automatic code fixer.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.standardrb.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "standardrb", "--lsp" }
```
- `filetypes` :
```lua
{ "ruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/standardrb.lua:4](../lua/lspconfig/configs/standardrb.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## starlark_rust
https://github.com/facebookexperimental/starlark-rust/
The LSP part of `starlark-rust` is not currently documented,
but the implementation works well for linting.
This gives valuable warnings for potential issues in the code,
but does not support refactorings.
It can be installed with cargo: https://crates.io/crates/starlark
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.starlark_rust.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "starlark", "--lsp" }
```
- `filetypes` :
```lua
{ "star", "bzl", "BUILD.bazel" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/starlark_rust.lua:2](../lua/lspconfig/configs/starlark_rust.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## starpls
https://github.com/withered-magic/starpls
`starpls` is an LSP implementation for Starlark. Installation instructions can be found in the project's README.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.starpls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "starpls" }
```
- `filetypes` :
```lua
{ "bzl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/starpls.lua:4](../lua/lspconfig/configs/starpls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## statix
https://github.com/nerdypepper/statix
lints and suggestions for the nix programming language
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.statix.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
docs: update configs.md skip-checks: true
2024-12-02 05:34:35 +00:00
{ "statix", "check", "--stdin" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `filetypes` :
```lua
{ "nix" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/statix.lua:4](../lua/lspconfig/configs/statix.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## steep
https://github.com/soutaro/steep
`steep` is a static type checker for Ruby.
You need `Steepfile` to make it work. Generate it with `steep init`.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.steep.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "steep", "langserver" }
```
- `filetypes` :
```lua
{ "ruby", "eruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/steep.lua:4](../lua/lspconfig/configs/steep.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## stimulus_ls
https://www.npmjs.com/package/stimulus-language-server
`stimulus-lsp` can be installed via `npm`:
```sh
npm install -g stimulus-language-server
```
or via `yarn`:
```sh
yarn global add stimulus-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.stimulus_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "stimulus-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "html", "ruby", "eruby", "blade", "php" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/stimulus_ls.lua:4](../lua/lspconfig/configs/stimulus_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## stylelint_lsp
https://github.com/bmatcuk/stylelint-lsp
`stylelint-lsp` can be installed via `npm`:
```sh
npm i -g stylelint-lsp
```
Can be configured by passing a `settings.stylelintplus` object to `stylelint_lsp.setup`:
```lua
require'lspconfig'.stylelint_lsp.setup{
settings = {
stylelintplus = {
-- see available options in stylelint-lsp documentation
}
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.stylelint_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "stylelint-lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "css", "less", "scss", "sugarss", "vue", "wxss" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/stylelint_lsp.lua:17](../lua/lspconfig/configs/stylelint_lsp.lua#L17)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2025-01-13 07:41:33 +00:00
## stylua3p_ls
https://github.com/antonk52/lua-3p-language-servers
3rd party Language Server for Stylua lua formatter
Snippet to enable the language server:
```lua
require'lspconfig'.stylua3p_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "stylua-3p-language-server" }
```
- `filetypes` :
```lua
{ "lua" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/stylua3p_ls.lua:4](../lua/lspconfig/configs/stylua3p_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## superhtml
https://github.com/kristoff-it/superhtml
HTML Language Server & Templating Language Library
This LSP is designed to tightly adhere to the HTML spec as well as enforcing
some additional rules that ensure HTML clarity.
If you want to disable HTML support for another HTML LSP, add the following
to your configuration:
```lua
require'lspconfig'.superhtml.setup {
filetypes = { 'superhtml' }
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.superhtml.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "superhtml", "lsp" }
```
- `filetypes` :
```lua
{ "superhtml", "html" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/superhtml.lua:2](../lua/lspconfig/configs/superhtml.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## svelte
https://github.com/sveltejs/language-tools/tree/master/packages/language-server
Note: assuming that [ts_ls](#ts_ls) is setup, full JavaScript/TypeScript support (find references, rename, etc of symbols in Svelte files when working in JS/TS files) requires per-project installation and configuration of [typescript-svelte-plugin](https://github.com/sveltejs/language-tools/tree/master/packages/typescript-plugin#usage).
`svelte-language-server` can be installed via `npm`:
```sh
npm install -g svelte-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.svelte.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "svelteserver", "--stdio" }
```
- `filetypes` :
```lua
{ "svelte" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/svelte.lua:4](../lua/lspconfig/configs/svelte.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## svlangserver
https://github.com/imc-trading/svlangserver
Language server for SystemVerilog.
`svlangserver` can be installed via `npm`:
```sh
$ npm install -g @imc-trading/svlangserver
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.svlangserver.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- SvlangserverBuildIndex: Instructs language server to rerun indexing
- SvlangserverReportHierarchy: Generates hierarchy for the given module
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "svlangserver" }
```
- `filetypes` :
```lua
{ "verilog", "systemverilog" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/svlangserver.lua:19](../lua/lspconfig/configs/svlangserver.lua#L19)
- `settings` :
```lua
{
systemverilog = {
includeIndexing = { "*.{v,vh,sv,svh}", "**/*.{v,vh,sv,svh}" }
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## svls
https://github.com/dalance/svls
Language server for verilog and SystemVerilog
`svls` can be installed via `cargo`:
```sh
cargo install svls
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.svls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "svls" }
```
- `filetypes` :
```lua
{ "verilog", "systemverilog" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/svls.lua:2](../lua/lspconfig/configs/svls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## swift_mesonls
https://github.com/JCWasmx86/Swift-MesonLSP
Meson language server written in Swift
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.swift_mesonls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "Swift-MesonLSP", "--lsp" }
```
- `filetypes` :
```lua
{ "meson" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/swift_mesonls.lua:4](../lua/lspconfig/configs/swift_mesonls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## syntax_tree
https://ruby-syntax-tree.github.io/syntax_tree/
A fast Ruby parser and formatter.
Syntax Tree is a suite of tools built on top of the internal CRuby parser. It
provides the ability to generate a syntax tree from source, as well as the
tools necessary to inspect and manipulate that syntax tree. It can be used to
build formatters, linters, language servers, and more.
```sh
gem install syntax_tree
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.syntax_tree.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "stree", "lsp" }
```
- `filetypes` :
```lua
{ "ruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/syntax_tree.lua:4](../lua/lspconfig/configs/syntax_tree.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tabby_ml
https://tabby.tabbyml.com/blog/running-tabby-as-a-language-server
Language server for Tabby, an opensource, self-hosted AI coding assistant.
`tabby-agent` can be installed via `npm`:
```sh
npm install --global tabby-agent
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tabby_ml.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tabby-agent", "--lsp", "--stdio" }
```
- `filetypes` :
```lua
{}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tabby_ml.lua:2](../lua/lspconfig/configs/tabby_ml.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tailwindcss
https://github.com/tailwindlabs/tailwindcss-intellisense
Tailwind CSS Language Server can be installed via npm:
```sh
npm install -g @tailwindcss/language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tailwindcss.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tailwindcss-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "aspnetcorerazor", "astro", "astro-markdown", "blade", "clojure", "django-html", "htmldjango", "edge", "eelixir", "elixir", "ejs", "erb", "eruby", "gohtml", "gohtmltmpl", "haml", "handlebars", "hbs", "html", "htmlangular", "html-eex", "heex", "jade", "leaf", "liquid", "markdown", "mdx", "mustache", "njk", "nunjucks", "php", "razor", "slim", "twig", "css", "less", "postcss", "sass", "scss", "stylus", "sugarss", "javascript", "javascriptreact", "reason", "rescript", "typescript", "typescriptreact", "vue", "svelte", "templ" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/tailwindcss.lua:4](../lua/lspconfig/configs/tailwindcss.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tailwindcss.lua:4](../lua/lspconfig/configs/tailwindcss.lua#L4)
- `settings` :
```lua
{
tailwindCSS = {
classAttributes = { "class", "className", "class:list", "classList", "ngClass" },
includeLanguages = {
eelixir = "html-eex",
eruby = "erb",
htmlangular = "html",
templ = "html"
},
lint = {
cssConflict = "warning",
invalidApply = "error",
invalidConfigPath = "error",
invalidScreen = "error",
invalidTailwindDirective = "error",
invalidVariant = "error",
recommendedVariantOrder = "warning"
},
validate = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## taplo
https://taplo.tamasfe.dev/cli/usage/language-server.html
Language server for Taplo, a TOML toolkit.
`taplo-cli` can be installed via `cargo`:
```sh
cargo install --features lsp --locked taplo-cli
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.taplo.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "taplo", "lsp", "stdio" }
```
- `filetypes` :
```lua
{ "toml" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/taplo.lua:2](../lua/lspconfig/configs/taplo.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tblgen_lsp_server
https://mlir.llvm.org/docs/Tools/MLIRLSP/#tablegen-lsp-language-server--tblgen-lsp-server
The Language Server for the LLVM TableGen language
`tblgen-lsp-server` can be installed at the llvm-project repository (https://github.com/llvm/llvm-project)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tblgen_lsp_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tblgen-lsp-server" }
```
- `filetypes` :
```lua
{ "tablegen" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tblgen_lsp_server.lua:4](../lua/lspconfig/configs/tblgen_lsp_server.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## teal_ls
https://github.com/teal-language/teal-language-server
Install with:
```
luarocks install teal-language-server
```
Optional Command Args:
* "--log-mode=by_date" - Enable logging in $HOME/.cache/teal-language-server. Log name will be date + pid of process
* "--log-mode=by_proj_path" - Enable logging in $HOME/.cache/teal-language-server. Log name will be project path + pid of process
* "--verbose=true" - Increases log level. Does nothing unless log-mode is set
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.teal_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "teal-language-server" }
```
- `filetypes` :
```lua
{ "teal" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/teal_ls.lua:4](../lua/lspconfig/configs/teal_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## templ
https://templ.guide
The official language server for the templ HTML templating language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.templ.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "templ", "lsp" }
```
- `filetypes` :
```lua
{ "templ" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/templ.lua:4](../lua/lspconfig/configs/templ.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## terraform_lsp
https://github.com/juliosueiras/terraform-lsp
Terraform language server
Download a released binary from
https://github.com/juliosueiras/terraform-lsp/releases.
From https://github.com/hashicorp/terraform-ls#terraform-ls-vs-terraform-lsp:
Both HashiCorp and the maintainer of terraform-lsp expressed interest in
collaborating on a language server and are working towards a _long-term_
goal of a single stable and feature-complete implementation.
For the time being both projects continue to exist, giving users the
choice:
- `terraform-ls` providing
- overall stability (by relying only on public APIs)
- compatibility with any provider and any Terraform >=0.12.0 currently
less features
- due to project being younger and relying on public APIs which may
not offer the same functionality yet
- `terraform-lsp` providing
- currently more features
- compatibility with a single particular Terraform (0.12.20 at time of writing)
- configs designed for other 0.12 versions may work, but interpretation may be inaccurate
- less stability (due to reliance on Terraform's own internal packages)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.terraform_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "terraform-lsp" }
```
- `filetypes` :
```lua
{ "terraform", "hcl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/terraform_lsp.lua:4](../lua/lspconfig/configs/terraform_lsp.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## terraformls
https://github.com/hashicorp/terraform-ls
Terraform language server
Download a released binary from https://github.com/hashicorp/terraform-ls/releases.
From https://github.com/hashicorp/terraform-ls#terraform-ls-vs-terraform-lsp:
Both HashiCorp and the maintainer of terraform-lsp expressed interest in
collaborating on a language server and are working towards a _long-term_
goal of a single stable and feature-complete implementation.
For the time being both projects continue to exist, giving users the
choice:
- `terraform-ls` providing
- overall stability (by relying only on public APIs)
- compatibility with any provider and any Terraform >=0.12.0 currently
less features
- due to project being younger and relying on public APIs which may
not offer the same functionality yet
- `terraform-lsp` providing
- currently more features
- compatibility with a single particular Terraform (0.12.20 at time of writing)
- configs designed for other 0.12 versions may work, but interpretation may be inaccurate
- less stability (due to reliance on Terraform's own internal packages)
Note, that the `settings` configuration option uses the `workspace/didChangeConfiguration` event,
[which is not supported by terraform-ls](https://github.com/hashicorp/terraform-ls/blob/main/docs/features.md).
Instead you should use `init_options` which passes the settings as part of the LSP initialize call
[as is required by terraform-ls](https://github.com/hashicorp/terraform-ls/blob/main/docs/SETTINGS.md#how-to-pass-settings).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.terraformls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "terraform-ls", "serve" }
```
- `filetypes` :
```lua
{ "terraform", "terraform-vars" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/terraformls.lua:4](../lua/lspconfig/configs/terraformls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## texlab
https://github.com/latex-lsp/texlab
A completion engine built from scratch for (La)TeX.
See https://github.com/latex-lsp/texlab/wiki/Configuration for configuration options.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.texlab.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- TexlabBuild: Build the current buffer
- TexlabCancelBuild: Cancel the current build
- TexlabChangeEnvironment: Change the environment at current position
- TexlabCleanArtifacts: Clean the artifacts
- TexlabCleanAuxiliary: Clean the auxiliary files
- TexlabDependencyGraph: Show the dependency graph
- TexlabFindEnvironments: Find the environments at current position
- TexlabForward: Forward search from current position
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "texlab" }
```
- `filetypes` :
```lua
{ "tex", "plaintex", "bib" }
```
docs: update configs.md skip-checks: true
2024-11-24 00:58:53 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/texlab.lua:159](../lua/lspconfig/configs/texlab.lua#L159)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
texlab = {
bibtexFormatter = "texlab",
build = {
args = { "-pdf", "-interaction=nonstopmode", "-synctex=1", "%f" },
executable = "latexmk",
forwardSearchAfter = false,
onSave = false
},
chktex = {
onEdit = false,
onOpenAndSave = false
},
diagnosticsDelay = 300,
formatterLineLength = 80,
forwardSearch = {
args = {}
},
latexFormatter = "latexindent",
latexindent = {
modifyLineBreaks = false
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## textlsp
https://github.com/hangyav/textLSP
`textLSP` is an LSP server for text spell and grammar checking with various AI tools.
It supports multiple text file formats, such as LaTeX, Org or txt.
For the available text analyzer tools and their configuration, see the [GitHub](https://github.com/hangyav/textLSP) page.
By default, all analyzers are disabled in textLSP, since most of them need special settings.
For quick testing, LanguageTool is enabled in the default `nvim-lspconfig` configuration.
To install run: `pip install textLSP`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.textlsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "textlsp" }
```
- `filetypes` :
```lua
{ "text", "tex", "org" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/textlsp.lua:2](../lua/lspconfig/configs/textlsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
textLSP = {
analysers = {
languagetool = {
check_text = {
on_change = false,
on_open = true,
on_save = true
},
enabled = true
}
},
documents = {
org = {
org_todo_keywords = { "TODO", "IN_PROGRESS", "DONE" }
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tflint
https://github.com/terraform-linters/tflint
A pluggable Terraform linter that can act as lsp server.
Installation instructions can be found in https://github.com/terraform-linters/tflint#installation.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tflint.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tflint", "--langserver" }
```
- `filetypes` :
```lua
{ "terraform" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tflint.lua:4](../lua/lspconfig/configs/tflint.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## theme_check
https://github.com/Shopify/shopify-cli
`theme-check-language-server` is bundled with `shopify-cli` or it can also be installed via
https://github.com/Shopify/theme-check#installation
**NOTE:**
If installed via Homebrew, `cmd` must be set to 'theme-check-liquid-server'
```lua
require lspconfig.theme_check.setup {
cmd = { 'theme-check-liquid-server' }
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.theme_check.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "theme-check-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "liquid" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/theme_check.lua:6](../lua/lspconfig/configs/theme_check.lua#L6)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## thriftls
https://github.com/joyme123/thrift-ls
you can install thriftls by mason or download binary here: https://github.com/joyme123/thrift-ls/releases
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.thriftls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "thriftls" }
```
- `filetypes` :
```lua
{ "thrift" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/thriftls.lua:4](../lua/lspconfig/configs/thriftls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tilt_ls
https://github.com/tilt-dev/tilt
Tilt language server.
You might need to add filetype detection manually:
```vim
autocmd BufRead Tiltfile setf=tiltfile
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tilt_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tilt", "lsp", "start" }
```
- `filetypes` :
```lua
{ "tiltfile" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tilt_ls.lua:2](../lua/lspconfig/configs/tilt_ls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tinymist
https://github.com/Myriad-Dreamin/tinymist
An integrated language service for Typst [taɪpst]. You can also call it "微霭" [wēi ǎi] in Chinese.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tinymist.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tinymist" }
```
- `filetypes` :
```lua
{ "typst" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tinymist.lua:2](../lua/lspconfig/configs/tinymist.lua#L2)
docs: update configs.md skip-checks: true
2024-12-12 08:35:15 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ts_ls
https://github.com/typescript-language-server/typescript-language-server
`ts_ls`, aka `typescript-language-server`, is a Language Server Protocol implementation for TypeScript wrapping `tsserver`. Note that `ts_ls` is not `tsserver`.
`typescript-language-server` depends on `typescript`. Both packages can be installed via `npm`:
```sh
npm install -g typescript typescript-language-server
```
To configure typescript language server, add a
[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) or
[`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig) to the root of your
project.
Here's an example that disables type checking in JavaScript files.
```json
{
"compilerOptions": {
"module": "commonjs",
"target": "es6",
"checkJs": false
},
"exclude": [
"node_modules"
]
}
```
### Vue support
As of 2.0.0, Volar no longer supports TypeScript itself. Instead, a plugin
adds Vue support to this language server.
*IMPORTANT*: It is crucial to ensure that `@vue/typescript-plugin` and `volar `are of identical versions.
```lua
require'lspconfig'.ts_ls.setup{
init_options = {
plugins = {
{
name = "@vue/typescript-plugin",
location = "/usr/local/lib/node_modules/@vue/typescript-plugin",
languages = {"javascript", "typescript", "vue"},
},
},
},
filetypes = {
"javascript",
"typescript",
"vue",
},
}
-- You must make sure volar is setup
-- e.g. require'lspconfig'.volar.setup{}
-- See volar's section for more information
```
`location` MUST be defined. If the plugin is installed in `node_modules`,
`location` can have any value.
`languages` must include `vue` even if it is listed in `filetypes`.
`filetypes` is extended here to include Vue SFC.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ts_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "typescript-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
```
- `init_options` :
```lua
{
hostInfo = "neovim"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ts_ls.lua:4](../lua/lspconfig/configs/ts_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-26 00:16:03 +00:00
## ts_query_ls
https://github.com/ribru17/ts_query_ls
Can be configured by passing a "settings" object to `ts_query_ls.setup{}`:
```lua
require('lspconfig').ts_query_ls.setup{
settings = {
parser_install_directories = {
-- If using nvim-treesitter with lazy.nvim
vim.fs.joinpath(
vim.fn.stdpath('data'),
'/lazy/nvim-treesitter/parser/'
),
},
-- This setting is provided by default
parser_aliases = {
ecma = 'javascript',
jsx = 'javascript',
php_only = 'php',
},
-- E.g. zed support
language_retrieval_patterns = {
'languages/src/([^/]+)/[^/]+\\.scm$',
},
},
}
```
Snippet to enable the language server:
```lua
require'lspconfig'.ts_query_ls.setup{}
```
Default config:
- `cmd` :
```lua
{ "ts_query_ls" }
```
- `filetypes` :
```lua
{ "query" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ts_query_ls.lua:4](../lua/lspconfig/configs/ts_query_ls.lua#L4)
- `settings` :
```lua
{
parser_aliases = {
ecma = "javascript",
jsx = "javascript",
php_only = "php"
}
}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tsp_server
https://github.com/microsoft/typespec
The language server for TypeSpec, a language for defining cloud service APIs and shapes.
`tsp-server` can be installed together with the typespec compiler via `npm`:
```sh
npm install -g @typespec/compiler
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tsp_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "tsp-server", "--stdio" }
```
- `filetypes` :
```lua
{ "typespec" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tsp_server.lua:4](../lua/lspconfig/configs/tsp_server.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ttags
https://github.com/npezza93/ttags
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ttags.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ttags", "lsp" }
```
- `filetypes` :
```lua
{ "ruby", "rust", "javascript", "haskell" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ttags.lua:4](../lua/lspconfig/configs/ttags.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## turtle_ls
https://github.com/stardog-union/stardog-language-servers/tree/master/packages/turtle-language-server
`turtle-language-server`, An editor-agnostic server providing language intelligence (diagnostics, hover tooltips, etc.) for the W3C standard Turtle RDF syntax via the Language Server Protocol.
installable via npm install -g turtle-language-server or yarn global add turtle-language-server.
requires node.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.turtle_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "node",
[3] = "--stdio"
}
```
- `filetypes` :
```lua
{ "turtle", "ttl" }
```
docs: update configs.md skip-checks: true
2024-12-21 15:10:48 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/turtle_ls.lua:28](../lua/lspconfig/configs/turtle_ls.lua#L28)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## tvm_ffi_navigator
https://github.com/tqchen/ffi-navigator
The Language Server for FFI calls in TVM to be able jump between python and C++
FFI navigator can be installed with `pip install ffi-navigator`, buf for more details, please see
https://github.com/tqchen/ffi-navigator?tab=readme-ov-file#installation
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.tvm_ffi_navigator.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "python", "-m", "ffi_navigator.langserver" }
```
- `filetypes` :
```lua
{ "python", "cpp" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/tvm_ffi_navigator.lua:4](../lua/lspconfig/configs/tvm_ffi_navigator.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## twiggy_language_server
https://github.com/moetelo/twiggy
`twiggy-language-server` can be installed via `npm`:
```sh
npm install -g twiggy-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.twiggy_language_server.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "twiggy-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "twig" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/twiggy_language_server.lua:4](../lua/lspconfig/configs/twiggy_language_server.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## typeprof
https://github.com/ruby/typeprof
`typeprof` is the built-in analysis and LSP tool for Ruby 3.1+.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.typeprof.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "typeprof", "--lsp", "--stdio" }
```
- `filetypes` :
```lua
{ "ruby", "eruby" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/typeprof.lua:4](../lua/lspconfig/configs/typeprof.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## typos_lsp
https://github.com/crate-ci/typos
https://github.com/tekumara/typos-lsp
A Language Server Protocol implementation for Typos, a low false-positive
source code spell checker, written in Rust. Download it from the releases page
on GitHub: https://github.com/tekumara/typos-lsp/releases
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.typos_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "typos-lsp" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/typos_lsp.lua:4](../lua/lspconfig/configs/typos_lsp.lua#L4)
- `settings` :
```lua
{}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## typst_lsp
https://github.com/nvarner/typst-lsp
Language server for Typst.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.typst_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "typst-lsp" }
```
- `filetypes` :
```lua
{ "typst" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/typst_lsp.lua:2](../lua/lspconfig/configs/typst_lsp.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## uiua
https://github.com/uiua-lang/uiua/
The builtin language server of the Uiua interpreter.
The Uiua interpreter can be installed with `cargo install uiua`
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.uiua.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "uiua", "lsp" }
```
- `filetypes` :
```lua
{ "uiua" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/uiua.lua:4](../lua/lspconfig/configs/uiua.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-04 06:39:10 +00:00
## ungrammar_languageserver
https://github.com/binhtran432k/ungrammar-language-features
Language Server for Ungrammar.
Ungrammar Language Server can be installed via npm:
```sh
npm i ungrammar-languageserver -g
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
```lua
require'lspconfig'.ungrammar_languageserver.setup{}
```
Default config:
- `cmd` :
```lua
{ "ungrammar-languageserver", "--stdio" }
```
- `filetypes` :
```lua
{ "ungrammar" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ungrammar_languageserver.lua:2](../lua/lspconfig/configs/ungrammar_languageserver.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
ungrammar = {
format = {
enable = true
},
validate = {
enable = true
docs: update configs.md skip-checks: true
2024-10-04 06:39:10 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-04 06:39:10 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## unison
https://github.com/unisonweb/unison/blob/trunk/docs/language-server.markdown
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.unison.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "nc", "localhost", "5757" }
```
- `filetypes` :
```lua
{ "unison" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/unison.lua:4](../lua/lspconfig/configs/unison.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## unocss
https://github.com/xna00/unocss-language-server
UnoCSS Language Server can be installed via npm:
```sh
npm i unocss-language-server -g
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.unocss.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "unocss-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "erb", "haml", "hbs", "html", "css", "postcss", "javascript", "javascriptreact", "markdown", "ejs", "php", "svelte", "typescript", "typescriptreact", "vue-html", "vue", "sass", "scss", "less", "stylus", "astro", "rescript", "rust" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/unocss.lua:4](../lua/lspconfig/configs/unocss.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## uvls
https://codeberg.org/caradhras/uvls
Language server for UVL, written using tree sitter and rust.
You can install the server easily using cargo:
```sh
git clone https://codeberg.org/caradhras/uvls
cd uvls
cargo install --path .
```
Note: To activate properly nvim needs to know the uvl filetype.
You can add it via:
```lua
docs: update configs.md skip-checks: true
2024-10-15 16:02:50 +00:00
vim.cmd([[au BufRead,BufNewFile *.uvl setfiletype uvl]])
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.uvls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "uvls" }
```
- `filetypes` :
```lua
{ "uvl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/uvls.lua:2](../lua/lspconfig/configs/uvls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## v_analyzer
https://github.com/vlang/v-analyzer
V language server.
`v-analyzer` can be installed by following the instructions [here](https://github.com/vlang/v-analyzer#installation).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.v_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "v-analyzer" }
```
- `filetypes` :
```lua
{ "v", "vsh", "vv" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/v_analyzer.lua:4](../lua/lspconfig/configs/v_analyzer.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vacuum
Vacuum is the worlds fastest OpenAPI 3, OpenAPI 2 / Swagger linter and quality analysis tool.
You can install vacuum using mason or follow the instructions here: https://github.com/daveshanley/vacuum
The file types are not detected automatically, you can register them manually (see below) or override the filetypes:
```lua
vim.filetype.add {
pattern = {
['openapi.*%.ya?ml'] = 'yaml.openapi',
['openapi.*%.json'] = 'json.openapi',
},
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vacuum.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vacuum", "language-server" }
```
- `filetypes` :
```lua
{ "yaml.openapi", "json.openapi" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vacuum.lua:2](../lua/lspconfig/configs/vacuum.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vala_ls
https://github.com/Prince781/vala-language-server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vala_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vala-language-server" }
```
- `filetypes` :
```lua
{ "vala", "genie" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vala_ls.lua:25](../lua/lspconfig/configs/vala_ls.lua#L25)
- `single_file_support` : `true`
regen docs
2024-10-24 15:06:10 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vale_ls
https://github.com/errata-ai/vale-ls
An implementation of the Language Server Protocol (LSP) for the Vale command-line tool.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vale_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vale-ls" }
```
- `filetypes` :
```lua
docs: update configs.md skip-checks: true
2024-11-17 13:00:46 +00:00
{ "markdown", "text", "tex", "rst" }
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vale_ls.lua:4](../lua/lspconfig/configs/vale_ls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vdmj
https://github.com/nickbattle/vdmj
The VDMJ language server can be installed by cloning the VDMJ repository and
running `mvn clean install`.
Various options are provided to configure the language server (see below). In
particular:
- `annotation_paths` is a list of folders and/or jar file paths for annotations
that should be used with the language server;
- any value of `debugger_port` less than zero will disable the debugger; note
that if a non-zero value is used, only one instance of the server can be active
at a time.
More settings for VDMJ can be changed in a file called `vdmj.properties` under
`root_dir/.vscode`. For a description of the available settings, see
[Section 7 of the VDMJ User Guide](https://raw.githubusercontent.com/nickbattle/vdmj/master/vdmj/documentation/UserGuide.pdf).
Note: proof obligations and combinatorial testing are not currently supported
by neovim.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vdmj.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "java" }
```
- `filetypes` :
```lua
{ "vdmsl", "vdmpp", "vdmrt" }
```
- `options` :
```lua
{
annotation_paths = {},
debugger_port = -1,
high_precision = false,
docs: update configs.md skip-checks: true
2024-12-17 07:22:31 +00:00
java = "/usr/lib/jvm/temurin-17-jdk-amd64/bin/java",
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
java_opts = { "-Xmx3000m", "-Xss1m" },
logfile = "/home/user/.cache/nvim/vdm-lsp.log",
mavenrepo = "/home/user/.m2/repository/com/fujitsu"
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vdmj.lua:44](../lua/lspconfig/configs/vdmj.lua#L44)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## verible
https://github.com/chipsalliance/verible
A linter and formatter for verilog and SystemVerilog files.
Release binaries can be downloaded from [here](https://github.com/chipsalliance/verible/releases)
and placed in a directory on PATH.
See https://github.com/chipsalliance/verible/tree/master/verilog/tools/ls/README.md for options.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.verible.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "verible-verilog-ls" }
```
- `filetypes` :
```lua
{ "systemverilog", "verilog" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/verible.lua:2](../lua/lspconfig/configs/verible.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## veridian
https://github.com/vivekmalneedi/veridian
A SystemVerilog LanguageServer.
Download the latest release for your OS from the releases page
# install with slang feature, if C++17 compiler is available
cargo install --git https://github.com/vivekmalneedi/veridian.git --all-features
# install if C++17 compiler is not available
cargo install --git https://github.com/vivekmalneedi/veridian.git
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.veridian.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "veridian" }
```
- `filetypes` :
```lua
{ "systemverilog", "verilog" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/veridian.lua:2](../lua/lspconfig/configs/veridian.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## veryl_ls
https://github.com/veryl-lang/veryl
Language server for Veryl
`veryl-ls` can be installed via `cargo`:
```sh
cargo install veryl-ls
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.veryl_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "veryl-ls" }
```
- `filetypes` :
```lua
{ "veryl" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/veryl_ls.lua:2](../lua/lspconfig/configs/veryl_ls.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vhdl_ls
Install vhdl_ls from https://github.com/VHDL-LS/rust_hdl and add it to path
Configuration
The language server needs to know your library mapping to perform full analysis of the code. For this it uses a configuration file in the TOML format named vhdl_ls.toml.
vhdl_ls will load configuration files in the following order of priority (first to last):
A file named .vhdl_ls.toml in the user home folder.
A file name from the VHDL_LS_CONFIG environment variable.
A file named vhdl_ls.toml in the workspace root.
Settings in a later files overwrites those from previously loaded files.
Example vhdl_ls.toml
```
# File names are either absolute or relative to the parent folder of the vhdl_ls.toml file
[libraries]
lib2.files = [
'pkg2.vhd',
]
lib1.files = [
'pkg1.vhd',
'tb_ent.vhd'
]
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vhdl_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vhdl_ls" }
```
- `filetypes` :
```lua
{ "vhd", "vhdl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vhdl_ls.lua:9](../lua/lspconfig/configs/vhdl_ls.lua#L9)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vimls
https://github.com/iamcco/vim-language-server
You can install vim-language-server via npm:
```sh
npm install -g vim-language-server
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vimls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vim-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "vim" }
```
- `init_options` :
```lua
{
diagnostic = {
enable = true
},
indexes = {
count = 3,
gap = 100,
projectRootPatterns = { "runtime", "nvim", ".git", "autoload", "plugin" },
runtimepath = true
},
isNeovim = true,
iskeyword = "@,48-57,_,192-255,-#",
runtimepath = "",
suggest = {
fromRuntimepath = true,
fromVimruntime = true
},
vimruntime = ""
}
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vimls.lua:2](../lua/lspconfig/configs/vimls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## visualforce_ls
https://github.com/forcedotcom/salesforcedx-vscode
Language server for Visualforce.
For manual installation, download the .vsix archive file from the
[forcedotcom/salesforcedx-vscode](https://github.com/forcedotcom/salesforcedx-vscode)
GitHub releases. Then, configure `cmd` to run the Node script at the unpacked location:
```lua
require'lspconfig'.visualforce_ls.setup {
cmd = {
'node',
'/path/to/unpacked/archive/extension/node_modules/@salesforce/salesforcedx-visualforce-language-server/out/src/visualforceServer.js',
'--stdio'
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.visualforce_ls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `filetypes` :
```lua
{ "visualforce" }
```
- `init_options` :
```lua
{
embeddedLanguages = {
css = true,
javascript = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/visualforce_ls.lua:4](../lua/lspconfig/configs/visualforce_ls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vls
https://github.com/vlang/vls
V language server.
`v-language-server` can be installed by following the instructions [here](https://github.com/vlang/vls#installation).
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "v", "ls" }
```
- `filetypes` :
```lua
{ "v", "vlang" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vls.lua:4](../lua/lspconfig/configs/vls.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## volar
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
https://github.com/vuejs/language-tools/tree/master/packages/language-server
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
Volar language server for Vue
Volar can be installed via npm:
```sh
npm install -g @vue/language-server
```
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
Volar by default supports Vue 3 projects.
For Vue 2 projects, [additional configuration](https://github.com/vuejs/language-tools/blob/master/extensions/vscode/README.md?plain=1#L19) are required.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
**Hybrid Mode (by default)**
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
In this mode, the Vue Language Server exclusively manages the CSS/HTML sections.
You need the `ts_ls` server with the `@vue/typescript-plugin` plugin to support TypeScript in `.vue` files.
See `ts_ls` section for more information
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
**No Hybrid Mode**
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
Volar will run embedded `ts_ls` therefore there is no need to run it separately.
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
local lspconfig = require('lspconfig')
lspconfig.volar.setup {
-- add filetypes for typescript, javascript and vue
filetypes = { 'typescript', 'javascript', 'javascriptreact', 'typescriptreact', 'vue' },
init_options = {
vue = {
-- disable hybrid mode
hybridMode = false,
},
},
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
-- you must remove ts_ls setup
-- lspconfig.ts_ls.setup {}
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```
**Overriding the default TypeScript Server used by Volar**
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
The default config looks for TypeScript in the local `node_modules`. This can lead to issues
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
e.g. when working on a [monorepo](https://monorepo.tools/). The alternatives are:
- use a global TypeScript Server installation
```lua
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
require'lspconfig'.volar.setup {
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
init_options = {
typescript = {
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
-- replace with your global TypeScript library path
tsdk = '/path/to/node_modules/typescript/lib'
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
}
```
- use a local server and fall back to a global TypeScript Server installation
```lua
docs: update configs.md skip-checks: true
2024-12-10 05:11:05 +00:00
require'lspconfig'.volar.setup {
init_options = {
typescript = {
-- replace with your global TypeScript library path
tsdk = '/path/to/node_modules/typescript/lib'
}
},
on_new_config = function(new_config, new_root_dir)
local lib_path = vim.fs.find('node_modules/typescript/lib', { path = new_root_dir, upward = true })[1]
if lib_path then
new_config.init_options.typescript.tsdk = lib_path
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
end
end
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.volar.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vue-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "vue" }
```
- `init_options` :
```lua
{
typescript = {
tsdk = ""
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/volar.lua:16](../lua/lspconfig/configs/volar.lua#L16)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/volar.lua:16](../lua/lspconfig/configs/volar.lua#L16)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-02 05:44:07 +00:00
## vscoqtop
https://github.com/coq-community/vscoq
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
docs: update configs.md skip-checks: true
2024-10-02 05:44:07 +00:00
```lua
require'lspconfig'.vscoqtop.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vscoqtop" }
```
- `filetypes` :
```lua
{ "coq" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vscoqtop.lua:4](../lua/lspconfig/configs/vscoqtop.lua#L4)
- `single_file_support` : `true`
docs: update configs.md skip-checks: true
2024-10-02 05:44:07 +00:00
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vtsls
https://github.com/yioneko/vtsls
`vtsls` can be installed with npm:
```sh
npm install -g @vtsls/language-server
```
To configure a TypeScript project, add a
[`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
or [`jsconfig.json`](https://code.visualstudio.com/docs/languages/jsconfig) to
the root of your project.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vtsls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vtsls", "--stdio" }
```
- `filetypes` :
```lua
{ "javascript", "javascriptreact", "javascript.jsx", "typescript", "typescriptreact", "typescript.tsx" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vtsls.lua:4](../lua/lspconfig/configs/vtsls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## vuels
https://github.com/vuejs/vetur/tree/master/server
Vue language server(vls)
`vue-language-server` can be installed via `npm`:
```sh
npm install -g vls
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.vuels.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "vls" }
```
- `filetypes` :
```lua
{ "vue" }
```
- `init_options` :
```lua
{
config = {
css = {},
emmet = {},
html = {
suggest = {}
},
javascript = {
format = {}
},
stylusSupremacy = {},
typescript = {
format = {}
},
vetur = {
completion = {
autoImport = false,
tagCasing = "kebab",
useScaffoldSnippets = false
regen docs
2024-10-24 15:06:10 +00:00
},
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
format = {
defaultFormatter = {
js = "none",
ts = "none"
regen docs
2024-10-24 15:06:10 +00:00
},
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
defaultFormatterOptions = {},
scriptInitialIndent = false,
styleInitialIndent = false
},
useWorkspaceDependencies = false,
validation = {
script = true,
style = true,
template = true
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/vuels.lua:4](../lua/lspconfig/configs/vuels.lua#L4)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## wgsl_analyzer
https://github.com/wgsl-analyzer/wgsl-analyzer
`wgsl_analyzer` can be installed via `cargo`:
```sh
cargo install --git https://github.com/wgsl-analyzer/wgsl-analyzer wgsl_analyzer
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.wgsl_analyzer.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "wgsl_analyzer" }
```
- `filetypes` :
```lua
{ "wgsl" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/wgsl_analyzer.lua:4](../lua/lspconfig/configs/wgsl_analyzer.lua#L4)
- `settings` :
```lua
{}
```
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## yamlls
https://github.com/redhat-developer/yaml-language-server
`yaml-language-server` can be installed via `yarn`:
```sh
yarn global add yaml-language-server
```
To use a schema for validation, there are two options:
1. Add a modeline to the file. A modeline is a comment of the form:
```
# yaml-language-server: $schema=<urlToTheSchema|relativeFilePath|absoluteFilePath}>
```
where the relative filepath is the path relative to the open yaml file, and the absolute filepath
is the filepath relative to the filesystem root ('/' on unix systems)
2. Associated a schema url, relative , or absolute (to root of project, not to filesystem root) path to
the a glob pattern relative to the detected project root. Check `:LspInfo` to determine the resolved project
root.
```lua
require('lspconfig').yamlls.setup {
... -- other configuration for setup {}
settings = {
yaml = {
... -- other settings. note this overrides the lspconfig defaults.
schemas = {
["https://json.schemastore.org/github-workflow.json"] = "/.github/workflows/*",
["../path/relative/to/file.yml"] = "/.github/workflows/*",
["/path/from/root/of/project"] = "/.github/workflows/*",
},
},
}
}
```
Currently, kubernetes is special-cased in yammls, see the following upstream issues:
* [#211](https://github.com/redhat-developer/yaml-language-server/issues/211).
* [#307](https://github.com/redhat-developer/yaml-language-server/issues/307).
To override a schema to use a specific k8s schema version (for example, to use 1.18):
```lua
require('lspconfig').yamlls.setup {
... -- other configuration for setup {}
settings = {
yaml = {
... -- other settings. note this overrides the lspconfig defaults.
schemas = {
["https://raw.githubusercontent.com/instrumenta/kubernetes-json-schema/master/v1.18.0-standalone-strict/all.json"] = "/*.k8s.yaml",
... -- other schemas
},
},
}
}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.yamlls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "yaml-language-server", "--stdio" }
```
- `filetypes` :
```lua
{ "yaml", "yaml.docker-compose", "yaml.gitlab" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/yamlls.lua:2](../lua/lspconfig/configs/yamlls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `settings` :
```lua
{
redhat = {
telemetry = {
enabled = false
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
}
}
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
}
```
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## yang_lsp
https://github.com/TypeFox/yang-lsp
A Language Server for the YANG data modeling language.
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.yang_lsp.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "yang-language-server" }
```
- `filetypes` :
```lua
{ "yang" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/yang_lsp.lua:2](../lua/lspconfig/configs/yang_lsp.lua#L2)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## yls
https://pypi.org/project/yls-yara/
An YLS plugin adding YARA linting capabilities.
This plugin runs yara.compile on every save, parses the errors, and returns list of diagnostic messages.
Language Server: https://github.com/avast/yls
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.yls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "yls", "-vv" }
```
- `filetypes` :
```lua
{ "yar", "yara" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/yls.lua:2](../lua/lspconfig/configs/yls.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ziggy
https://ziggy-lang.io/documentation/ziggy-lsp/
Language server for the Ziggy data serialization format
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ziggy.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ziggy", "lsp" }
```
- `filetypes` :
```lua
{ "ziggy" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ziggy.lua:2](../lua/lspconfig/configs/ziggy.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## ziggy_schema
https://ziggy-lang.io/documentation/ziggy-lsp/
Language server for schema files of the Ziggy data serialization format
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.ziggy_schema.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "ziggy", "lsp", "--schema" }
```
- `filetypes` :
```lua
{ "ziggy_schema" }
```
docs: update configs.md skip-checks: true
2024-12-14 16:24:25 +00:00
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/ziggy_schema.lua:2](../lua/lspconfig/configs/ziggy_schema.lua#L2)
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## zk
https://github.com/mickael-menu/zk
A plain text note-taking assistant
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.zk.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Commands:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
- ZkIndex: ZkIndex
- ZkList: ZkList
- ZkNew: ZkNew
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "zk", "lsp" }
```
- `filetypes` :
```lua
{ "markdown" }
```
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/zk.lua:12](../lua/lspconfig/configs/zk.lua#L12)
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
## zls
https://github.com/zigtools/zls
Zig LSP implementation + Zig Language Server
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Snippet to enable the language server:
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
```lua
require'lspconfig'.zls.setup{}
```
feat(docs): improve formatting of generated docs #3400
2024-10-24 17:28:14 +00:00
Default config:
- `cmd` :
```lua
{ "zls" }
```
- `filetypes` :
```lua
{ "zig", "zir" }
```
- `on_new_config` source (use "gF" to visit): [../lua/lspconfig/configs/zls.lua:4](../lua/lspconfig/configs/zls.lua#L4)
- `root_dir` source (use "gF" to visit): [../lua/lspconfig/configs/zls.lua:4](../lua/lspconfig/configs/zls.lua#L4)
- `single_file_support` : `true`
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
docs: update configs.md skip-checks: true
2024-10-06 10:40:19 +00:00
<!--
refactor: rename "server_configurations" => "configs" #3330 Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
2024-10-01 12:39:12 +00:00
vim:ft=markdown
docs: update configs.md skip-checks: true
2024-10-06 10:40:19 +00:00
-->
Reference in New Issue Copy Permalink