Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Adds support for multiple editor workspaces on initialization | Roberto Vidal | 2019-04-14 | 1 | -7/+0 | |
| | | | | This is a quick, partial fix for #1104 | |||||
* | Fix eslint errors | Emil Lauridsen | 2019-04-03 | 1 | -1/+1 | |
| | ||||||
* | Add extra double quotes only on Windows. | Emil Lauridsen | 2019-04-03 | 1 | -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 Lauridsen | 2019-04-03 | 1 | -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 refactoring | Edwin Cheng | 2019-04-02 | 2 | -44/+78 | |
| | ||||||
* | Fix prettier error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | ||||||
* | Add terminate process implemntation note | Edwin Cheng | 2019-04-02 | 1 | -0/+7 | |
| | ||||||
* | Add Cargo.toml file check before cargo watch start | Edwin Cheng | 2019-04-02 | 1 | -0/+22 | |
| | ||||||
* | Add cargo-watch.check-arguments | Edwin Cheng | 2019-04-02 | 5 | -74/+137 | |
| | ||||||
* | Add config for cargo-watch trace | Edwin Cheng | 2019-04-02 | 4 | -15/+66 | |
| | ||||||
* | Add proper process teminate method | Edwin Cheng | 2019-04-02 | 6 | -10/+116 | |
| | ||||||
* | Fix prettier error | Edwin Cheng | 2019-04-02 | 4 | -22/+31 | |
| | ||||||
* | Fixed tslint error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | ||||||
* | Fix tslint error | Edwin Cheng | 2019-04-02 | 2 | -63/+65 | |
| | ||||||
* | Improve cargo-watch usage | Edwin Cheng | 2019-04-02 | 4 | -36/+177 | |
| | ||||||
* | kill ra.el: it is superseeded by the lsp integraion | Aleksey Kladov | 2019-03-30 | 1 | -128/+0 | |
| | ||||||
* | Fix emacs-lsp runnables support with native json | Florian Diebold | 2019-03-28 | 1 | -1/+1 | |
| | | | | (In that case args is a vector, which string-join doesn't like.) | |||||
* | Don't execute cargo watch when popup is dismissed | pcpthm | 2019-03-22 | 1 | -2/+2 | |
| | ||||||
* | Change enableCargoWatchOnStartup to have three states | Ville Penttinen | 2019-03-21 | 3 | -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. | |||||
* | introduce docs dir | Aleksey Kladov | 2019-03-20 | 1 | -241/+0 | |
| | ||||||
* | Appease CI | Igor Matuszewski | 2019-03-18 | 1 | -9/+7 | |
| | ||||||
* | Guard auto cargo watch behind a config option | Igor Matuszewski | 2019-03-18 | 3 | -0/+17 | |
| | ||||||
* | 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 | |
| | ||||||
* | Fix ra-emacs-lsp for newest lsp-mode with native json support | Florian Diebold | 2019-03-14 | 1 | -5/+4 | |
| | ||||||
* | Fix typo | Florian Gilcher | 2019-03-13 | 1 | -1/+1 | |
| | ||||||
* | activate extension if Cargo.toml is present | Aleksey Kladov | 2019-03-13 | 1 | -1/+2 | |
| | ||||||
* | 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 | |
| | ||||||
* | Merge branch 'master' of https://github.com/LDSpits/rust-analyzer into ↵ | Lucas Spits | 2019-03-11 | 1 | -2/+2 | |
|\ | | | | | | | feature/workspace-directory | |||||
| * | prettier format | Bernardo | 2019-03-10 | 1 | -1/+1 | |
| | | ||||||
| * | simplify watch patterns | Bernardo | 2019-03-10 | 1 | -3/+3 | |
| | | ||||||
* | | Retrieve current directory from workspaces | Lucas Spits | 2019-03-11 | 1 | -2/+18 | |
|/ | ||||||
* | Add showWorkspaceLoadedNotification to vscode client | Ville Penttinen | 2019-03-06 | 3 | -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 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 | 3 | -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. | |||||
* | emacs: Fix (void-variable rust-analyzer--last-runnable) | Florian Diebold | 2019-03-03 | 1 | -1/+1 | |
| | ||||||
* | Change default value of highlightingOn to false | Ville Penttinen | 2019-02-26 | 1 | -1/+1 | |
| | ||||||
* | emacs-lsp: Add runnables support | Florian Diebold | 2019-02-23 | 1 | -4/+40 | |
| | ||||||
* | Use named multiline Problem Matcher | kjeremy | 2019-02-18 | 1 | -29/+2 | |
| | | | | | Now that https://github.com/Microsoft/vscode/pull/65840 is in the latest release we can use the first commit from https://github.com/rust-analyzer/rust-analyzer/pull/408 | |||||
* | Add my emacs configuration | Florian Diebold | 2019-02-16 | 1 | -0/+139 | |
| | | | | | This relies on emacs-lsp instead of eglot, so I didn't want to just add it to the other one. | |||||
* | Merge #807 | bors[bot] | 2019-02-12 | 1 | -1/+1 | |
|\ | | | | | | | | | | | | | | | | | | | 807: Specify vscode 1.31 r=matklad a=kjeremy This is for #796 It doesn't seem to fix the problem if you manually install the extension but it is the "right thing to do". Co-authored-by: kjeremy <kjeremy@gmail.com> | |||||
| * | Specify vscode 1.31 | kjeremy | 2019-02-12 | 1 | -1/+1 | |
| | |