| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Specifically, when we tear down IO threads, we should take care to
dispose connection.
closes #1775
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
closes #1474
|
|
|
|
|
|
| |
This wasn't a right decision in the first place, the feature flag was
broken in the last rustfmt release, and syntax highlighting of imports
is more important anyway
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The issue was windows specific -- cancellation caused collection of
bracktraces at some point, and that was slow on windows.
The proper fix here is to make sure that we don't collect bracktraces
unnecessary (which we currently do due to failure), but, as a
temporary fix, let's just not force their collection in the first
place!
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is a quick, partial fix for #1104
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows users to control whether or not they want to see the "workspace
loaded" notification.
This is done on the server side using InitializationOptions which are provided
by the client. By default show_workspace_loaded is true, meaning the
notification is sent.
|
|
|
|
|
|
|
| |
This now allows us to send a notification that can be shown in the UI when the
workspace has been loaded.
Additionally this removes the need for internal_mode flag.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
302: WIP: Support tracing lsp requests. r=DJMcNab a=DJMcNab
EDIT: We need to work out a better way to handle settings before this can be merged. Help wanted
TODO: Debug why decorations are sent even when highlightingOn is disabled
This makes the log volume so high its impossible to work with anyway.
(Continuation of #84 [#99 only disabled using it, not making sure we don't send it]).
These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/
Co-authored-by: DJMcNab <[email protected]>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
See https://github.com/Microsoft/language-server-protocol/issues/567
for motivations to not require `InitializationOptions`
TODO: Check if there are any other protocol extensions
which should be disabled if not implemented on the client
|
| |
| |
| |
| |
| |
| |
| |
| | |
This isn't working properly because we don't dynamically disable or enable it
TODO: work out why highlighting can be enabled mid session.
TODO: Improve settings handling
|
|/ |
|
|
|
|
|
|
|
| |
This fixes a common problem when running under VS Code, the user
doesn't have permissions to create a `log` directory in the CWD.
The old behavior can be re-enabled by setting RA_INTERNAL_MODE=1
|
| |
|
| |
|
|
|
|
| |
It is used in this file
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Run `cargo fmt` and ignore generated files
|
| |
|
|
|