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

I am using this extension as part of the coc-sh plugin for coc.nvim. When I am doing the file completion, I do not see hidden files and directories suggested. Is there a way to enable this?

Motivation

Currently the language server stores symbols (i.e. variables, classes, ...) in two locations:

• The source path, containing the parsed .kt source files from the user's workspace
• The [class path](https://github.com/fwcd/kotlin-language-server/blob/master/server/

Is your feature request related to a problem? Please describe.
Provide basic support for pug markup. Related: #106

Describe the solution you'd like
VSCode's syntax highlight is done by Textmate grammar. Basically it's defining some regex pattern to tokenize the code. And we could include other languages' rules as long as vscode knows how to deal with the included language.

I am n

Since the extension is only proof of concept and not on the marketplace, we can't easily update the server when a new release comes out. I have a local gulp setup to automate some tasks but it still a bit of a process to update a server. It would be great to be able to update the lsp server from inside vscode without rebuilding and installing the extension (especially now that releases are happeni

Current Version

0.5.3

Use-cases

Currently we only expose rootModulePaths in "LSP native" configuration:

https://github.com/hashicorp/terraform-ls/blob/a1ff20f9f5378eaf2b224f84c8bc05b2028da18f/internal/settings/settings.go#L11-L13

Some runtime settings which we don't strictly need to know before the server is actually initialized is still exposed via CLI flags onl

At this point the descriptions of the plugin options visible in the Atom settings are rather basic and often less accurate than what can be found in the documentation of the specific feature provider.

We should improve those descriptions and/or link to the relevant docs if applicable.

Any help on this is highly apprec