Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Change enableCargoWatchOnStartup to have three states | Ville Penttinen | 2019-03-21 | 2 | -13/+18 | |
| | | | | | | | This fixes #1005. Defaults to `ask` which prompts users each time whether to start `cargo watch` or not. `enabled` always starts `cargo watch` and `disabled` does not. | |||||
* | Appease CI | Igor Matuszewski | 2019-03-18 | 1 | -9/+7 | |
| | ||||||
* | Guard auto cargo watch behind a config option | Igor Matuszewski | 2019-03-18 | 2 | -0/+12 | |
| | ||||||
* | Separate out the interactive cargo watch procedure | Igor Matuszewski | 2019-03-18 | 2 | -64/+70 | |
| | ||||||
* | Reformat using Prettier | Igor Matuszewski | 2019-03-18 | 2 | -17/+35 | |
| | ||||||
* | Remove unused imports | Igor Matuszewski | 2019-03-18 | 1 | -2/+1 | |
| | ||||||
* | Prefer installing `cargo-watch` via Task API | Igor Matuszewski | 2019-03-18 | 1 | -23/+14 | |
| | | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors. | |||||
* | Respect the user-provided label when creating task | Igor Matuszewski | 2019-03-18 | 1 | -1/+1 | |
| | ||||||
* | Ask the user to install and start cargo watch | Igor Matuszewski | 2019-03-18 | 1 | -5/+61 | |
| | ||||||
* | Define a cargo watch task | Igor Matuszewski | 2019-03-18 | 1 | -1/+21 | |
| | ||||||
* | Remove redundant Runnable.range | Igor Matuszewski | 2019-03-18 | 1 | -1/+0 | |
| | ||||||
* | Applied code style of ``npm run fix`` | Lucas Spits | 2019-03-11 | 1 | -6/+4 | |
| | ||||||
* | Fix typescript linting errors | Lucas Spits | 2019-03-11 | 1 | -1/+1 | |
| | ||||||
* | Retrieve current directory from workspaces | Lucas Spits | 2019-03-11 | 1 | -2/+18 | |
| | ||||||
* | Add showWorkspaceLoadedNotification to vscode client | Ville Penttinen | 2019-03-06 | 2 | -1/+10 | |
| | | | | | | | | | 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. | |||||
* | Allow syntax tree to update when changing files | Ville Penttinen | 2019-03-03 | 2 | -17/+26 | |
| | | | | | | Previously when using the file based syntax tree, it would not update until a change had been made in the new file. Now we automatically update the syntax tree to match the current file. | |||||
* | Rename syntaxtree text provider to SyntaxTreeContentProvider | Ville Penttinen | 2019-03-03 | 3 | -13/+11 | |
| | ||||||
* | Add vscode support for range in SyntaxTreeParams | Ville Penttinen | 2019-03-03 | 2 | -10/+40 | |
| | | | | | | This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range. | |||||
* | Fix trace and prettier | DJMcNab | 2019-02-10 | 1 | -2/+4 | |
| | ||||||
* | Add support for a seperate output channel for trace messages | DJMcNab | 2019-02-10 | 1 | -2/+5 | |
| | ||||||
* | Run prettier | Ville Penttinen | 2019-02-07 | 1 | -4/+11 | |
| | ||||||
* | Add new configuration "enableEnhancedTyping" to control registering of ↵ | Ville Penttinen | 2019-02-07 | 2 | -1/+28 | |
| | | | | | | | | | | | | | | | | | | "type" command This further fixes problems when having a VIM extension (at least vscodevim) enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when enableEnhancedTyping is set to `false`. The problem is dependent on the order in which extensions are activated, if rust-analyzer is activated before `vscodevim`, rust-analyzer will register the `type` command, and when `vscodevim` finally attempts to activate, it will fail to register the command. This causes `vscodevim` to stop working properly. This setting allows users to disable the registerCommand `type` in rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`. Currently changing the setting requires reloading of the window. | |||||
* | Implement lens for impls and support resolving lenses. | Jeremy Kolb | 2019-02-04 | 1 | -0/+12 | |
| | ||||||
* | Clear the console when running single tasks | kjeremy | 2019-01-30 | 1 | -1/+2 | |
| | ||||||
* | align command naming | Aleksey Kladov | 2019-01-28 | 12 | -30/+47 | |
| | ||||||
* | add gc request | Aleksey Kladov | 2019-01-25 | 1 | -0/+3 | |
| | ||||||
* | better stats | Aleksey Kladov | 2019-01-25 | 2 | -7/+59 | |
| | ||||||
* | ad status command | Aleksey Kladov | 2019-01-22 | 3 | -0/+15 | |
| | ||||||
* | Config for raLspServerPath will be overwritten if __RA_LSP_SERVER_DEBUG is set | Andrew Ross | 2019-01-19 | 1 | -2/+5 | |
| | | | | | | | Changed presentation from clear to reveal silent Removed the vscode gitignore entry Added debugging documentation Added tasks and launch configs | |||||
* | Prettier fix | Alan Du | 2019-01-15 | 1 | -1/+4 | |
| | ||||||
* | Reveal the newly added source change in the editor. | Jeremy A. Kolb | 2019-01-14 | 1 | -0/+1 | |
| | ||||||
* | npm fix run | Jeremy Kolb | 2019-01-12 | 4 | -9/+16 | |
| | ||||||
* | Move run_single into runnables | Jeremy Kolb | 2019-01-12 | 4 | -66/+17 | |
| | ||||||
* | Code lens support for running tests | Jeremy A. Kolb | 2019-01-11 | 3 | -0/+68 | |
| | ||||||
* | Allow user to set path to ra_lsp_server in vscode settings | gentoo90 | 2019-01-05 | 2 | -1/+6 | |
| | ||||||
* | fix open of created or renamed file | Bernardo | 2019-01-05 | 1 | -1/+2 | |
| | ||||||
* | use lsp WorkspaceEdit instead of custom source_file_edits and file_system_edits | Bernardo | 2019-01-03 | 1 | -33/+10 | |
| | ||||||
* | highlight macro idents | Aleksey Kladov | 2018-12-28 | 1 | -1/+2 | |
| | ||||||
* | Merge #302 | bors[bot] | 2018-12-24 | 1 | -1/+25 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]> | |||||
| * | Add a very hacky workaround to not trace decorations requests | DJMcNab | 2018-12-24 | 1 | -1/+25 | |
| | | ||||||
* | | Fix analyzer extension fail when there are enabled any VIM extension. | frai | 2018-12-22 | 1 | -13/+17 | |
|/ | ||||||
* | use new clear-terminal feature | Aleksey Kladov | 2018-12-15 | 1 | -2/+2 | |
| | ||||||
* | Remove uneeded characters | DJMcNab | 2018-12-08 | 1 | -3/+3 | |
| | ||||||
* | Fix on enter | Adolfo Ochagavía | 2018-11-09 | 1 | -2/+2 | |
| | ||||||
* | workspace-symbols function for Emacs | Aleksey Kladov | 2018-11-08 | 1 | -1/+4 | |
| | ||||||
* | Rename File -> SourceFileNode | Aleksey Kladov | 2018-11-07 | 1 | -2/+2 | |
| | ||||||
* | Fully add inline modules to module tree | Aleksey Kladov | 2018-11-05 | 2 | -9/+8 | |
| | ||||||
* | Fix typo | Pascal Hertleif | 2018-10-21 | 1 | -1/+1 | |
| | | | Truly an A+, errrr, +a commit | |||||
* | Fold multiline comments | Adolfo Ochagavía | 2018-10-12 | 1 | -2/+2 | |
| | ||||||
* | Remove error publishing through publishDecorations | Adolfo Ochagavía | 2018-10-10 | 1 | -7/+0 | |
| |