Bug Description:

The argument "useCapture" is used in the addEventListener function, so it should also appears in the removeEventListener function

Additional Information

• Operating System:
• Theia Version: ma

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

While I quite like the information readily provided by g:lsp_diagnostics_float_cursor and g:lsp_diagnostics_echo_cursor, their automatic nature doesn't fit my workflow.

Would it be difficult to add an avenue to trigger them on-demand, similar to <plug>(lsp-hover) / :LspHover?

Along similar lines, would it be difficult to add a g:lsp... setting to have <plug>(lsp-next-diganostic)

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

The current display of:

should be improved to include:

• name of the file that has no issues (so just in case if the user has focus on a different file they are not confused)
• padding so that the text is more readable
• a nice "congrats"

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Ubuntu 19.04
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used: virtualenv

Problem

The type hints in the stub file for the current module aren't used for autocompletion.

I have a foo.pyi file as

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

Often, something goes wrong in my setup of kak-lsp (a language server is installed incorrectly, the command I specified for that LSP is wrong, the plugin just isn't enabled for the window, I forgot to start the LSP, my kak-lsp.toml is invalid or in the wrong place, my code project is setup wrong, etc., etc.) When this happens there are two problems that make it more difficult to solve:

1. **T

Ranch is a dependency used by the TCP transport in Erlang LS (see the els_tcp module). The new version of ranch, 2.0.0 has a slightly backward incompatible API and we should migrate to it.

A migration guide is available at: https://ninenines.eu/docs/en/ranch/2.0/guide/migrating_from_1.7/

Expected Behavior

I would like to be warned that an "in port" would be stripped if no subscription is implemented.

Current Behavior

port module Main exposing (..)

-- Define an inPort (but no implementation yet)
port inPort : (String -> msg) -> Sub msg

subscriptions : Model -> Sub Msg
subscriptions _ =
    Sub.none -- inPort is never subscribed to

Current