about summary refs log tree commit diff
path: root/editors/code
AgeCommit message (Collapse)AuthorLines
2019-03-03Allow syntax tree to update when changing filesVille Penttinen-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.
2019-03-03Rename syntaxtree text provider to SyntaxTreeContentProviderVille Penttinen-13/+11
2019-03-03Add vscode support for range in SyntaxTreeParamsVille Penttinen-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.
2019-02-26Change default value of highlightingOn to falseVille Penttinen-1/+1
2019-02-18Use named multiline Problem Matcherkjeremy-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
2019-02-12Specify vscode 1.31kjeremy-1/+1
2019-02-10Update dependenciesDJMcNab-8/+8
2019-02-10Fix trace and prettierDJMcNab-2/+4
2019-02-10Add support for a seperate output channel for trace messagesDJMcNab-10/+13
2019-02-07Update npm packageskjeremy-99/+65
2019-02-07Run prettierVille Penttinen-4/+11
2019-02-07Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen-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.
2019-02-04Implement lens for impls and support resolving lenses.Jeremy Kolb-0/+12
2019-01-30Merge #704 #705bors[bot]-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 <36049421+djmcnab@users.noreply.github.com> Co-authored-by: Jeremy Kolb <kjeremy@gmail.com>
2019-01-30Clear the console when running single taskskjeremy-1/+2
2019-01-29Add category to the commandsDJMcNab-8/+16
2019-01-29Start the extension when rust-analyzer status is runDJMcNab-1/+3
2019-01-28align command namingAleksey Kladov-55/+72
2019-01-25add gc requestAleksey Kladov-0/+7
2019-01-25better statsAleksey Kladov-7/+59
2019-01-23ad status commandAleksey Kladov-0/+19
2019-01-19Address issues flagged in reviewMarcus Klaas de Vries-45/+45
2019-01-19Add additional pattern variantsMarcus Klaas de Vries-45/+45
2019-01-19Config for raLspServerPath will be overwritten if __RA_LSP_SERVER_DEBUG is setAndrew Ross-2/+5
Changed presentation from clear to reveal silent Removed the vscode gitignore entry Added debugging documentation Added tasks and launch configs
2019-01-15Prettier fixAlan Du-1/+4
2019-01-15Fail Travis on Prettier formatting issueAlan Du-1/+1
2019-01-14Reveal the newly added source change in the editor.Jeremy A. Kolb-0/+1
2019-01-13:arrow_up: npmAleksey Kladov-69/+69
2019-01-12npm fix runJeremy Kolb-9/+16
2019-01-12Move run_single into runnablesJeremy Kolb-66/+17
2019-01-11Code lens support for running testsJeremy A. Kolb-0/+68
2019-01-05Allow user to set path to ra_lsp_server in vscode settingsgentoo90-1/+13
2019-01-05fix open of created or renamed fileBernardo-1/+2
2019-01-03index stuff produced by macrosAleksey Kladov-437/+437
2019-01-03use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo-33/+10
2019-01-01named multiline problem patterns are not parsed properly in vscode at the momentBernardo-2/+29
2019-01-01fix regex and add rustc-watch problem matcherBernardo-23/+32
2018-12-28highlight macro identsAleksey Kladov-1/+2
2018-12-24Merge #302bors[bot]-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 <36049421+djmcnab@users.noreply.github.com>
2018-12-24Add a very hacky workaround to not trace decorations requestsDJMcNab-1/+25
2018-12-22Fix analyzer extension fail when there are enabled any VIM extension.frai-13/+17
2018-12-20Support tracing lsp requests.DJMcNab-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
2018-12-19Reload package-lock.jsonDJMcNab-72/+78
2018-12-15use new clear-terminal featureAleksey Kladov-15/+15
2018-12-09remove direct dep on event-stream: malisious version was unpublishedAleksey Kladov-126/+39
2018-12-08Add package command and upgrade event-streamDJMcNab-4/+20
2018-12-08Run npm update and add private and preview flagsDJMcNab-721/+785
Private stops npm publish working, which would be nonsensical anyway In case it gets added to the vscode extension repository, preview marks it as such Private may also prevent publishing to the vscode extension repository
2018-12-08Remove uneeded charactersDJMcNab-3/+3
2018-12-08Improve the extend keybinding to not conflictDJMcNab-1/+1
2018-11-27fix npm problemsAleksey Kladov-39/+24
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-06-29 18:32:30 +0000