aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
...
| * "rust-analyzer.newDebugConfig" commandvsrs2020-05-111-0/+5
| |
| * "rust-analyzer.debug" commandvsrs2020-05-111-0/+5
| |
* | Merge #4400bors[bot]2020-05-131-0/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4400: Enhanced coloring r=georgewfraser a=georgewfraser This PR builds on #4397 to enhance the existing syntax coloring. ## Underline mutable variables The textmate scope `markup.underline` underlines identifiers, which is a nice way to make mutable vars stand out: <img width="327" alt="Screen Shot 2020-05-09 at 1 18 55 PM" src="https://user-images.githubusercontent.com/1369240/81484179-8bb47d80-91f8-11ea-997d-1dcffbe44aa7.png"> ## Italicize static variables The textmate scope `markup.italic` italicizes identifiers. Italic = static is a common convention in IDEs like IntelliJ: <img width="288" alt="Screen Shot 2020-05-09 at 1 19 14 PM" src="https://user-images.githubusercontent.com/1369240/81484236-cd452880-91f8-11ea-8478-505ee49bc8b3.png"> Co-authored-by: George Fraser <[email protected]>
| * | Leave statics aloneGeorge Fraser2020-05-121-3/+0
| | |
| * | Mark up statics and mutablesGeorge Fraser2020-05-121-0/+6
| | |
* | | Bump packageskjeremy2020-05-131-8/+8
| | |
* | | vscode engine 1.45kjeremy2020-05-121-1/+1
|/ / | | | | | | latest stable
* | Use .rust suffix on scopesGeorge Fraser2020-05-121-9/+9
| |
* | Change lifetimes back to keyword-ish, tweak builtins for consistency between ↵George Fraser2020-05-101-1/+1
| | | | | | | | TextMate and semantic
* | Import built-in textmate grammar, with no changesGeorge Fraser2020-05-101-0/+5
| |
* | Tweak the textmate fallback scopes to be consistent with builtin TextMate ↵George Fraser2020-05-101-8/+8
|/ | | | grammar and other languages
* Merge remote-tracking branch 'upstream/master' into uniformed_debug_lensvsrs2020-05-081-1/+15
|\ | | | | | | | | # Conflicts: # editors/code/src/commands/runnables.ts
| * Add master config for inlayHints to make disabling easyAleksey Kladov2020-05-081-0/+5
| |
| * Use the correct color for structsAleksey Kladov2020-05-071-0/+3
| | | | | | | | This works around https://github.com/microsoft/vscode/issues/97162
| * Better mapping to TextMate scopes for keywordsAleksey Kladov2020-05-061-0/+6
| | | | | | | | https://github.com/microsoft/vscode/issues/94367#issuecomment-608629883
| * package.json: Minor configuration spelling fixSean Bright2020-05-061-1/+1
| |
* | "rust-analyzer.debug.openDebugPane"vsrs2020-05-081-1/+1
| | | | | | Co-authored-by: bjorn3 <[email protected]>
* | Add CodeLLDB Rust visualizationvsrs2020-05-071-1/+1
| |
* | Add separate settings for each debug engine.vsrs2020-05-071-2/+2
| |
* | Add additional debug optionsvsrs2020-05-071-0/+10
|/
* Drop dead code and a dependency!veetaha2020-05-051-1/+0
|
* add the allFeatures flag (true by default)guigui642020-05-051-0/+5
|
* Merge #4166bors[bot]2020-05-051-0/+8
|\ | | | | | | | | | | | | | | 4166: Defining a default target to support cross-compilation targets r=matklad a=FuriouZz Related to #4163 Co-authored-by: Christophe MASSOLIN <[email protected]>
| * Rename `defaultTarget` to targetChristophe MASSOLIN2020-05-051-2/+2
| |
| * [config] rename cargo.defaultTargetChristophe MASSOLIN2020-04-271-1/+1
| |
| * Started rust-analyzer.cargo.defaultTarget implementationChristophe MASSOLIN2020-04-261-0/+8
| |
* | Fix typo in markdownDescriptionszunami2020-05-041-1/+1
| |
* | Specify cotributed semanticTokenTypes in package.jsonAleksey Kladov2020-05-041-0/+4
| |
* | Remove `workspaceLoaded` settingAndrew Chin2020-05-021-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `workspaceLoaded` notification setting was originally designed to control the display of a popup message that said: "workspace loaded, {} rust packages" This popup was removed and replaced by a much sleeker message in the VSCode status bar that provides a real-time status while loading: rust-analyzer: {}/{} packages This was done as part of #3587 The new status-bar indicator is unobtrusive and shouldn't need to be disabled. So this setting is removed.
* | Merge #4222bors[bot]2020-04-301-0/+22
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4222: Introduce C/C++ for Visual Studio Code extension as an alternative debug engine for Debug Code lens. r=matklad a=vsrs At the moment Debug Code Lens can use only one debug engine: lldb via [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) extension. This PR adds support of the debug engine from the [MS C++ tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) extension, as well as the configuration option. If both extensions are installed, `CodeLLDB` will be used by default. Another new option `rust-analyzer.debug.sourceFileMap` allows, for example, to step into Rust std library during debugging. Works only with `MS C++ tools`. On Windows: ```json "rust-analyzer.debug.sourceFileMap": { "/rustc/4fb7144ed159f94491249e86d5bbd033b5d60550": "${env:USERPROFILE}/.rustup/toolchains/stable-x86_64-pc-windows-msvc/lib/rustlib/src/rust" } ``` On Linux: ```json "rust-analyzer.debug.sourceFileMap": { "/rustc/4fb7144ed159f94491249e86d5bbd033b5d60550": "~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust" } ``` Co-authored-by: vsrs <[email protected]>
| * | pass Cargo errors to the Debug output channelvsrs2020-04-301-1/+1
| | |
| * | better configuration enum itemsvsrs2020-04-291-11/+14
| | |
| * | Configuration settings and source maps supportvsrs2020-04-291-0/+19
| |/
* / Build extension tooJonas Schievink2020-04-281-0/+1
|/
* Disable onEnter command by defaultAleksey Kladov2020-04-231-5/+0
| | | | | We are transitioning from experimental to production-ready stance, so it makes sense to disable potentially disruptive features by default.
* Merge #4090bors[bot]2020-04-221-1/+1
|\ | | | | | | | | | | | | | | | | 4090: Fix config naming r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Align the name of proc-macro enabling flagAleksey Kladov2020-04-221-1/+1
| | | | | | | | We use `enable`, not `enabled` elsewhere
* | npm updatekjeremy2020-04-221-7/+7
|/
* Add semantic tag for unresolved referencesAleksey Kladov2020-04-181-0/+4
| | | | | | | | | | | This is a quick way to implement unresolved reference diagnostics. For example, adding to VS Code config "editor.tokenColorCustomizationsExperimental": { "unresolvedReference": "#FF0000" }, will highlight all unresolved refs in red.
* Add proc-macro cli command for rust-analyzerEdwin Cheng2020-04-161-5/+0
|
* Add config for proc_macroEdwin Cheng2020-04-161-0/+10
|
* Merge #3962bors[bot]2020-04-151-1/+1
|\ | | | | | | | | | | | | | | 3962: Fix parentModule shortcut conflict r=matklad a=CodeSandwich The default parentModule shortcut conflicts with VSCode's built-in undo selection Co-authored-by: Igor Żuk <[email protected]>
| * Fix parentModule shortcut conflictIgor Żuk2020-04-131-1/+1
| | | | | | The default parentModule shortcut conflicts with VSCode's built-in undo selection
* | Bump @types/vscode and vscode-languageclientkjeremy2020-04-141-2/+2
|/
* Enable the SemanticTokensFeature by defaultkjeremy2020-04-081-6/+1
| | | | | | | This is covered under vscode's "editor.semanticHighlighting.enabled" setting plus the user has to have a theme that has opted into highlighting. Bumps required vscode stable to 1.44
* Update some packageskjeremy2020-04-071-3/+3
|
* Better config scheme & defaultsAleksey Kladov2020-04-071-6/+14
|
* Merge pull request #3853 from matklad/cfAleksey Kladov2020-04-061-4/+1
|\ | | | | Make control token modifier less ambiguous
| * Make control token modifier less ambiguousAleksey Kladov2020-04-061-4/+1
| | | | | | | | | | | | | | | | | | In textmate, keyword.control is used for all kinds of things; in fact, the default scope mapping for keyword is keyword.control! So let's add a less ambiguous controlFlow modifier See Microsoft/vscode#94367
* | vscode: restore removed default valuesveetaha2020-04-041-0/+5
|/ | | | | | | | After refactoring the config we forgot to set defaults for some properties like workspaceLoaded, callInfo.full, etc. This commit restored them to being turned on by defult, as well added defaults for other props to be more explicit on their defualt value.
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-06 00:59:10 +0100