aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
*-. Merge #704 #705bors[bot]2019-01-301-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 commandsDJMcNab2019-01-291-8/+16
| | |
| * | Start the extension when rust-analyzer status is runDJMcNab2019-01-291-1/+3
| |/
* / Clear the console when running single taskskjeremy2019-01-301-1/+2
|/
* align command namingAleksey Kladov2019-01-2814-56/+73
|
* add gc requestAleksey Kladov2019-01-252-0/+7
|
* better statsAleksey Kladov2019-01-252-7/+59
|
* ad status commandAleksey Kladov2019-01-224-0/+19
|
* Address issues flagged in reviewMarcus Klaas de Vries2019-01-191-45/+45
|
* Add additional pattern variantsMarcus Klaas de Vries2019-01-191-45/+45
|
* Config for raLspServerPath will be overwritten if __RA_LSP_SERVER_DEBUG is setAndrew Ross2019-01-191-2/+5
| | | | | | | Changed presentation from clear to reveal silent Removed the vscode gitignore entry Added debugging documentation Added tasks and launch configs
* Prettier fixAlan Du2019-01-151-1/+4
|
* Fail Travis on Prettier formatting issueAlan Du2019-01-151-1/+1
|
* Reveal the newly added source change in the editor.Jeremy A. Kolb2019-01-141-0/+1
|
* :arrow_up: npmAleksey Kladov2019-01-132-69/+69
|
* note about performanceAleksey Kladov2019-01-131-7/+18
|
* Merge #521bors[bot]2019-01-131-55/+166
|\ | | | | | | | | | | | | | | 521: refresh docs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * refresh docsAleksey Kladov2019-01-131-55/+166
| |
* | npm fix runJeremy Kolb2019-01-124-9/+16
|/
* Merge #500bors[bot]2019-01-122-0/+19
|\ | | | | | | | | | | | | | | | | | | | | 500: Code lens support for running tests r=matklad a=kjeremy Supports running individual and mod tests. I feel like this kind of abuses the `Runnables` infrastructure but it works. Maybe later on down the line we should introduce a struct that is really just a tuple of binary, arguments, and environment and pass that back to the client instead. `run_single.ts` is just a paired down version of `runnables.ts` and there is duplication because I think run_single will probably change independent of runnables. Co-authored-by: Jeremy A. Kolb <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Move run_single into runnablesJeremy Kolb2019-01-124-66/+17
| |
| * Code lens support for running testsJeremy A. Kolb2019-01-113-0/+68
| |
* | Do not recommend fetching whole repo for end usersPaweł Zmarzły2019-01-121-1/+1
|/ | | `--depth 1` will make a shallow clone, of master branch only.
* Allow user to set path to ra_lsp_server in vscode settingsgentoo902019-01-053-1/+13
|
* fix open of created or renamed fileBernardo2019-01-051-1/+2
|
* index stuff produced by macrosAleksey Kladov2019-01-032-437/+437
|
* use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo2019-01-031-33/+10
|
* named multiline problem patterns are not parsed properly in vscode at the momentBernardo2019-01-011-2/+29
|
* fix regex and add rustc-watch problem matcherBernardo2019-01-011-23/+32
|
* Document formatting capabilitiesAleksander Vognild Burkow2018-12-291-0/+2
|
* highlight macro identsAleksey Kladov2018-12-281-1/+2
|
* Clarify installation prodecudeAleksey Kladov2018-12-271-0/+2
|
* Merge #302bors[bot]2018-12-242-1/+36
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 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 requestsDJMcNab2018-12-241-1/+25
| |
| * Support tracing lsp requests.DJMcNab2018-12-201-0/+11
| | | | | | | | | | | | TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway
* | Fix analyzer extension fail when there are enabled any VIM extension.frai2018-12-221-13/+17
|/
* Reload package-lock.jsonDJMcNab2018-12-191-72/+78
|
* use new clear-terminal featureAleksey Kladov2018-12-153-15/+15
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 13:22:37 +0000