aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* kill ra.el: it is superseeded by the lsp integraionAleksey Kladov2019-03-301-128/+0
|
* Fix emacs-lsp runnables support with native jsonFlorian Diebold2019-03-281-1/+1
| | | | (In that case args is a vector, which string-join doesn't like.)
* 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.
* introduce docs dirAleksey Kladov2019-03-201-241/+0
|
* 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
|
* Fix ra-emacs-lsp for newest lsp-mode with native json supportFlorian Diebold2019-03-141-5/+4
|
* Fix typoFlorian Gilcher2019-03-131-1/+1
|
* 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.
* emacs: Fix (void-variable rust-analyzer--last-runnable)Florian Diebold2019-03-031-1/+1
|
* Change default value of highlightingOn to falseVille Penttinen2019-02-261-1/+1
|
* emacs-lsp: Add runnables supportFlorian Diebold2019-02-231-4/+40
|
* Use named multiline Problem Matcherkjeremy2019-02-181-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 configurationFlorian Diebold2019-02-161-0/+139
| | | | | This relies on emacs-lsp instead of eglot, so I didn't want to just add it to the other one.
* Merge #807bors[bot]2019-02-121-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 <[email protected]>
| * Specify vscode 1.31kjeremy2019-02-121-1/+1
| |
* | mention no compatability guranteeAleksey Kladov2019-02-121-0/+3
|/
* Mention node.js requirement in readmeMatthias Einwag2019-02-101-1/+9
|
* Update dependenciesDJMcNab2019-02-102-8/+8
|
* Fix trace and prettierDJMcNab2019-02-101-2/+4
|
* Add support for a seperate output channel for trace messagesDJMcNab2019-02-103-10/+13
|
* Update npm packageskjeremy2019-02-072-99/+65
|
* Run prettierVille Penttinen2019-02-071-4/+11
|
* Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen2019-02-073-1/+33
| | | | | | | | | | | | | | | | | | "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 Kolb2019-02-041-0/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-05 02:16:15 +0100