Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 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 <[email protected]> | ||||
| * | Specify vscode 1.31 | kjeremy | 2019-02-12 | 1 | -1/+1 |
| | | |||||
* | | mention no compatability gurantee | Aleksey Kladov | 2019-02-12 | 1 | -0/+3 |
|/ | |||||
* | Mention node.js requirement in readme | Matthias Einwag | 2019-02-10 | 1 | -1/+9 |
| | |||||
* | Update dependencies | DJMcNab | 2019-02-10 | 2 | -8/+8 |
| | |||||
* | 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 | 3 | -10/+13 |
| | |||||
* | Update npm packages | kjeremy | 2019-02-07 | 2 | -99/+65 |
| | |||||
* | Run prettier | Ville Penttinen | 2019-02-07 | 1 | -4/+11 |
| | |||||
* | Add new configuration "enableEnhancedTyping" to control registering of ↵ | Ville Penttinen | 2019-02-07 | 3 | -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 Kolb | 2019-02-04 | 1 | -0/+12 |
| | |||||
*-. | Merge #704 #705 | bors[bot] | 2019-01-30 | 1 | -9/+19 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 704: Feat/jinstall lsp r=matklad a=DJMcNab Add `cargo jinstall-lsp` as a shorthand to include jemalloc support Also activate the extension when the commands are run which is makes sense to activate. I still need to work out what `Run` actually does to give it a better name, and other extensions through some voodoo magic are able to hide their commands from the command palette before the extension is activated, which would be a better fix. 705: Pass Documentation up to LSP and add "rust" to our codeblocks there r=matklad a=kjeremy Fixes #699 Co-authored-by: DJMcNab <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]> | ||||
| * | | Add category to the commands | DJMcNab | 2019-01-29 | 1 | -8/+16 |
| | | | |||||
| * | | Start the extension when rust-analyzer status is run | DJMcNab | 2019-01-29 | 1 | -1/+3 |
| |/ | |||||
* / | Clear the console when running single tasks | kjeremy | 2019-01-30 | 1 | -1/+2 |
|/ | |||||
* | align command naming | Aleksey Kladov | 2019-01-28 | 14 | -56/+73 |
| | |||||
* | add gc request | Aleksey Kladov | 2019-01-25 | 2 | -0/+7 |
| |