lsp-server
Here are 64 public repositories matching this topic...
-
Updated
Aug 16, 2021 - C++
Your environment
Output of haskell-language-server --probe-tools or haskell-language-server-wrapper --probe-tools:
haskell-language-server version: 1.3.0.0 (GHC: 9.0.1) (PATH: $PATH/haskell-language-server) (GIT hash: 2857eeece0398e1cd4b2ffb6069b05c4d2308b39)
Tool versions found on the $PATH
cabal: 3.4.0.0-
Updated
Apr 29, 2021 - Python
-
Updated
Jul 31, 2021 - Go
nimlsp crashes when opening file that imports cligen and threadpool modules. Without threadpool import it works fine. On CentOS 7, nim 1.4.8 and neovim 0.5.0 builtin lsp client.
the message was
nimsuggest instance for project /home/user/tmp stopped with exitcode: 1
Small example to reproduce the issue:
import threadpool
import cligen
proc f1(s: string) =
echo s
proc f2(
Find project file
-
Updated
Aug 13, 2021 - Crystal
-
Updated
Aug 12, 2021 - TypeScript
-
Updated
Aug 14, 2021 - Python
-
Updated
Aug 25, 2021 - TypeScript
-
Updated
Apr 15, 2021 - D
-
Updated
Aug 25, 2021 - JavaScript
-
Updated
Jan 23, 2021 - C++
-
Updated
Aug 26, 2021 - Kotlin
-
Updated
Dec 11, 2019 - Java
for instance
<setBody id="setBody10">
--
<constant>
<![CDATA[
<v1:isAliveResponse xmlns:v1="http://model.ws.xxxx.com/global/v1">
<isAlive>true</isAlive>
</v1:isAliveResponse>
]]>
</constant>
</setBody>
More information such as documentation text and predefined kinds can be added to what the completions provide.
-
Updated
Jun 12, 2021 - Go
-
Updated
Mar 3, 2019 - OCaml
-
Updated
Aug 11, 2019 - JavaScript
-
Updated
Aug 21, 2021 - TypeScript
-
Updated
Aug 24, 2021 - C++
-
Updated
Jan 17, 2019 - TypeScript
-
Updated
Aug 22, 2021 - Rust
-
Updated
Aug 20, 2021 - TypeScript
-
Updated
Aug 18, 2021 - Java
-
Updated
Jul 13, 2021 - Shell
-
Updated
Aug 26, 2021 - TypeScript
-
Updated
Sep 24, 2018 - Java
Improve this page
Add a description, image, and links to the lsp-server topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lsp-server topic, visit your repo's landing page and select "manage topics."
We currently use
logfor logging, but we also pull intracingthrough Chalk, and the nesting structure oftracingmight be a good fit for us anyway. So, we should switch totracingeverywhere.