language-server-protocol

Bug Description

cc rust-lang/rls#1112
cc microsoft/language-server-protocol#376

This causes problems with displaying correct diagnostic span and code suggestion spans (here).

Is your feature request related to a problem? Please describe.

Every time i run PlugUpdate on Windows it fails to replace bin/languageclient file. The reason is that on Windows it's impossible to overwrite binary if it's launched because file is busy.

Describe the solution you'd like

Some command to kill languageclient binary, so i can change my after update script to first kill lan

Elevator Pitch

Right now Jupyter LSP show it's suggestions on every period. I'd like to have a feature that only generates the suggestions when a hotkey is pressed. (Shift Tab, etc)

Motivation

One of my users asked for the feature.

Design Ideas

Document the commands that clients should implement and their expected behaviour on https://github.com/eclipse/eclipse.jdt.ls/wiki/JDT-LS-Extensions

Add a test workspace with a Maven project (similar to the Gradle project in server/src/test/resources/additionalWorkspace) and a test case in ClassPathTest to make sure that we don't regress on anything regarding dependency resolution in Maven projects.

Refiled from an old issue at JakeBecker/elixir-ls#120 (by @crbelaus)

The simplest suggestion I saw was simply adding a config option to disable automatic builds. See comment from @toranb for a potential spot to put the config check.

Related ideas for helping similar issues:

1. Add support

Test case

typedef dv_base_env_cov #(.CFG_T(tl_agent_env_cfg)) tl_agent_env_cov;

Actual output

typedef dv_base_env_cov#(.CFG_T(tl_agent_env_cfg)) tl_agent_env_cov;

Expected or suggested output (original formatting)

typedef dv_base_env_cov #(.CFG_T(tl_agent_env_cfg)) tl_agent_env_cov;

Verible version:

Context

One of the core features provided by Erlang LS is code navigation, which allows the user to jump from the current location to the corresponding definition. This mechanism works for functions, macros, records and more. The way code navigation works is by means of a database of points of interest which Erlang LS keeps in memory for each project. When accessing a project for the fir