about summary refs log tree commit diff
path: root/editors/code/src
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-10/+40
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-10Fix trace and prettierDJMcNab-2/+4
2019-02-10Add support for a seperate output channel for trace messagesDJMcNab-2/+5
2019-02-07Run prettierVille Penttinen-4/+11
2019-02-07Add new configuration "enableEnhancedTyping" to control registering of ↵Ville Penttinen-1/+28
"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-30Clear the console when running single taskskjeremy-1/+2
2019-01-28align command namingAleksey Kladov-30/+47
2019-01-25add gc requestAleksey Kladov-0/+3
2019-01-25better statsAleksey Kladov-7/+59
2019-01-23ad status commandAleksey Kladov-0/+15
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-14Reveal the newly added source change in the editor.Jeremy A. Kolb-0/+1
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/+6
2019-01-05fix open of created or renamed fileBernardo-1/+2
2019-01-03use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo-33/+10
2018-12-28highlight macro identsAleksey Kladov-1/+2
2018-12-24Merge #302bors[bot]-1/+25
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-15use new clear-terminal featureAleksey Kladov-2/+2
2018-12-08Remove uneeded charactersDJMcNab-3/+3
2018-11-09Fix on enterAdolfo Ochagavía-2/+2
2018-11-08workspace-symbols function for EmacsAleksey Kladov-1/+4
2018-11-07Rename File -> SourceFileNodeAleksey Kladov-2/+2
2018-11-05Fully add inline modules to module treeAleksey Kladov-9/+8
2018-10-21Fix typoPascal Hertleif-1/+1
Truly an A+, errrr, +a commit
2018-10-12Fold multiline commentsAdolfo Ochagavía-2/+2
2018-10-10Remove error publishing through publishDecorationsAdolfo Ochagavía-7/+0
2018-10-09Format vscode extension and add npm run fixAdolfo Ochagavía-14/+28
2018-10-09Add on-enter handlerAleksey Kladov-2/+51
Now, typing doc comments is much more pleasant
2018-10-08Run prettier on all filesDaniel McNab-102/+203
2018-10-08Add tslint and prettier to ciDaniel McNab-13/+13
2018-10-08Add some commentsAdolfo Ochagavía-25/+44
2018-10-08Fix remaining tslint suggestionsAdolfo Ochagavía-77/+81
2018-10-07Apply tslint suggestions, round oneAdolfo Ochagavía-242/+245
2018-10-07Refactor vscode extensionAdolfo Ochagavía-415/+518
2018-10-06Dynamically apply highlightingOn configAdolfo Ochagavía-11/+36
Fixes #84
2018-09-29Add a setting to disable custom syntax highlightingAdolfo Ochagavía-4/+12
2018-09-16goto super places cursor on modAleksey Kladov-0/+1
2018-09-16rename all thingsAleksey Kladov-0/+400