lsp

Is your feature request related to a problem? Please describe.
In Scala 2 it's possible to have completions after new CompletedName@@. It would be good to have the same for Scala 3.

Describe the solution you'd like
The potential solutions should take a look at NewCompletions.scala and related tests to see what needs to be supported but in general we would need:

• completions when

Description

Signature suggestion highlight color is unreadable in dark mode. It is a bright yellow which makes the white text completely unreadable. Reporting this as a bug b/c text becomes completely unreadable (probably not a bug if its just hard to read)

![Screen Shot 2022-04-15 at 11 54 37 AM](https://user-images.githubusercontent.com/17993489/163622448-50a0d6d5-232c-4dc0-8cef-22af67c

Here is a list of events: https://microsoft.github.io/debug-adapter-protocol/specification#Events. We currently don't handle all of them; they should be added to the dap--on-event.

The message "No message handler for ..." indicates that we don't implement some event.

Add a configuration flag that disables the Java-to-Kotlin converter in external sources. This would also require declaring the option in the vscode-kotlin client.

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

Hi,
i am using lsp-ui together with ivy in minibuffer mode. Unfortunately the doc popup with position bottom always overlaps the minibuffer making symbol lookup barely usable.

This is how it looks:

My lsp-ui config in case i caused this by some setting:

  (setq lsp-ui-si

Describe the bug

If you have (import-vars |my-ns/q), calling find-definition could take you to any definition of q, in any ns, not just in my-ns.

It should go to the var from the imported ns. To fix this we should use :imported-ns and :imported-var to convert the var-definition into a var-usage, and call find-definition :var-usages.

Depends on hashicorp/terraform-ls#722

Background

We have recently introduced a custom command module.calls which currently exclusively uses the data from the .terraform folder. There is currently no other easy way of getting the important metadata, such as (1) module hierarchy, (2) installed location on disk, (3) installed version.

As described

Restore previous presets defined here but make them opt-in.

Utilize @astier suggestions from #12

Context

One of the core features provided by Erlang LS is to provide inline documentation on hover. The way inline documentation 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 first time, Erlang LS scans every file in the project and extracts all point of interests (e.g. a function definition, or a f

If I run

printf 
session   = "1234"
client    = "client0"
buffile   = "foo.py"
filetype  = "python"
version   = 1
method    = "textDocument/definition"
[params.position]
line      = 5
column    = 1 | kak-lsp -s 1234 --request

It automatically trigger an action ( jump to definition in this example ) in the kakoune client

How can I just get the string of the action to perfor