aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
...
* Address feedbackLaurențiu Nicola2019-05-212-31/+21
|
* Use ThemeColor and add support for light themesLaurențiu Nicola2019-05-212-13/+141
|
* Pass `--all-targets` to `cargo watch`Aleksi Juvani2019-05-211-1/+1
|
* switch to official extend selection APIAleksey Kladov2019-04-215-45/+1
|
* :arrow_up: codeAleksey Kladov2019-04-212-1442/+185
|
* start cargo watch if not started interactivelyBernardo2019-04-193-3/+20
|
* recover rustc-watch problemMatchersBernardo2019-04-191-0/+12
|
* cargo watch start and stop commandsBernardo2019-04-195-55/+100
|
* PrettierRoberto Vidal2019-04-161-2/+1
|
* Fixes unrelated process termination quirkRoberto Vidal2019-04-161-0/+0
|
* Adds "restart server" commandRoberto Vidal2019-04-162-1/+20
|
* Sends cwd info for runnables and code lensesRoberto Vidal2019-04-141-1/+2
|
* Adds support for multiple editor workspaces on initializationRoberto Vidal2019-04-141-7/+0
| | | | This is a quick, partial fix for #1104
* Fix eslint errorsEmil Lauridsen2019-04-031-1/+1
|
* Add extra double quotes only on Windows.Emil Lauridsen2019-04-031-0/+4
| | | | | | As tested by @edwin0cheng, Windows requires the quotes removed in the previous commit. This commit re-adds the quotes gated by an if statement on the node environment, so that quotes are only added on Windows.
* Fix VSCode cargo-watch functionality on Linux.Emil Lauridsen2019-04-031-2/+1
| | | | | | | | | | | | | As of #1079 the VSCode cargo-watch functionality has been broken on Linux systems. The cause seems to be that linux takes the added quotes inside process arguments literally, so it attempts to make cargo-watch run the command `cargo "check --message-format json"` with the entire quoted part being treated as a single long subcommand, which cargo doesn't know how to handle. Removing the extra quotes solves the issue.
* Add cargo-watch package animation and refactoringEdwin Cheng2019-04-022-44/+78
|
* Fix prettier errorEdwin Cheng2019-04-021-1/+1
|
* Add terminate process implemntation noteEdwin Cheng2019-04-021-0/+7
|
* Add Cargo.toml file check before cargo watch startEdwin Cheng2019-04-021-0/+22
|
* Add cargo-watch.check-argumentsEdwin Cheng2019-04-025-74/+137
|
* Add config for cargo-watch traceEdwin Cheng2019-04-024-15/+66
|
* Add proper process teminate methodEdwin Cheng2019-04-026-10/+116
|
* Fix prettier errorEdwin Cheng2019-04-024-22/+31
|
* Fixed tslint errorEdwin Cheng2019-04-021-1/+1
|
* Fix tslint errorEdwin Cheng2019-04-022-63/+65
|
* Improve cargo-watch usageEdwin Cheng2019-04-024-36/+177
|
* Don't execute cargo watch when popup is dismissedpcpthm2019-03-221-2/+2
|
* Change enableCargoWatchOnStartup to have three statesVille Penttinen2019-03-213-16/+31
| | | | | | | 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 CIIgor Matuszewski2019-03-181-9/+7
|
* Guard auto cargo watch behind a config optionIgor Matuszewski2019-03-183-0/+17
|
* Separate out the interactive cargo watch procedureIgor Matuszewski2019-03-182-64/+70
|
* Reformat using PrettierIgor Matuszewski2019-03-182-17/+35
|
* Remove unused importsIgor Matuszewski2019-03-181-2/+1
|
* Prefer installing `cargo-watch` via Task APIIgor Matuszewski2019-03-181-23/+14
| | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors.
* Respect the user-provided label when creating taskIgor Matuszewski2019-03-181-1/+1
|
* Ask the user to install and start cargo watchIgor Matuszewski2019-03-181-5/+61
|
* Define a cargo watch taskIgor Matuszewski2019-03-181-1/+21
|
* Remove redundant Runnable.rangeIgor Matuszewski2019-03-181-1/+0
|
* activate extension if Cargo.toml is presentAleksey Kladov2019-03-131-1/+2
|
* Applied code style of ``npm run fix``Lucas Spits2019-03-111-6/+4
|
* Fix typescript linting errorsLucas Spits2019-03-111-1/+1
|
* Merge branch 'master' of https://github.com/LDSpits/rust-analyzer into ↵Lucas Spits2019-03-111-2/+2
|\ | | | | | | feature/workspace-directory
| * prettier formatBernardo2019-03-101-1/+1
| |
| * simplify watch patternsBernardo2019-03-101-3/+3
| |
* | Retrieve current directory from workspacesLucas Spits2019-03-111-2/+18
|/
* Add showWorkspaceLoadedNotification to vscode clientVille Penttinen2019-03-063-1/+15
| | | | | | | | | 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 filesVille Penttinen2019-03-032-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 SyntaxTreeContentProviderVille Penttinen2019-03-033-13/+11
|
* Add vscode support for range in SyntaxTreeParamsVille Penttinen2019-03-033-11/+41
| | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 03:49:15 +0000