This is the editor.action.showHover command. It is bound to cmdk cmdi by default. Note: Shortcut works by holding down the cmd [ctrl in windows], then while holding press k then i You can change the keyboard shortcut with a keybinding such as: { “key”: “cmd+k ctrl+space”, “command”: “editor.action.showHover”, “when”: “editorTextFocus” }
tmLanguage scope names are based on convention, so there’s no definitive list. The “Naming Conventions” section at the bottom of this TextMate Manual page is fairly comprehensive though. You can also check what scopes are highlighted by VSCode’s default themes, see for instance dark_plus.json and dark_vs.json (which the former is based on / includes). Finally, … Read more
OK, I finally figured out what the problem was. There are two ways you can change the comment blocks: 1. Configuration file I don’t know why it’s not in the documentation (or at least I couldn’t find it), but there is an optional property you pass to the object inside the contributes.languages array in the … Read more
This is the editor.action.showHover command. It is bound to cmdk cmdi by default. Note: Shortcut works by holding down the cmd [ctrl in windows], then while holding press k then i You can change the keyboard shortcut with a keybinding such as: { “key”: “cmd+k ctrl+space”, “command”: “editor.action.showHover”, “when”: “editorTextFocus” }
It’s possible with the new version 0.9.0. There’s an official documentation on how to add a custom language: https://github.com/microsoft/vscode-docs/blob/main/release-notes/v0_9_0.md You need a .tmLanguage file for the language you want to add. You can find existing files e.g. on GitHub or you can define your own language file. Look here to get an idea of how … Read more
You can use infinite-width lookahead and lookbehind without any constraint now beginning with Visual Studio Code v.1.31.0 release. See proof: and another one (with (?<=@fmt\([^()]*)\w+ pattern, note the * in the lookbehind): See the Github [VSCode 1.31] ES2018 RegExp lookbehind assertions are now supported #68004 issue: As a result of moving to Electron 3.0, RegExp … Read more