猫史档案馆

Integrated Terminal Removal of several prompt-related commands

The following commands have been removed:

• workbench.action.terminal.deleteWordLeft
• workbench.action.terminal.deleteWordRight
• workbench.action.terminal.deleteToLineStart
• workbench.action.terminal.moveToLineStart
• workbench.action.terminal.moveToLineEnd

These commands worked by sending a particular character sequence to the terminal, which was a best effort guess based on what command keybindings terminals use. The problem with these commands was that they were a black box, you needed to literally search through the vscode codebase to figure out how they worked. They have been replaced with custom keybindings for the workbench.action.terminal.sendSequence command, which does the same thing in a generic way.

These are advanced keyboard shortcuts and cannot be viewed in their entirety via the Keyboard Shortcuts UI as they contain arguments but you can view their JSON definitions by running the Preferences: Open Default Keyboard Shortcuts (JSON) command:

This should also help you learn how to use the powerful sendSequence command.

Support for pasting of multi-line text in PowerShell

Multi-line pasting never worked in PowerShell as VS Code always sent over the text in exactly the same way as typing it out. As explained above, several keybindings have been swapped to use the workbench.action.terminal.sendSequence command and you might have noticed a new keybinding was added for Windows only:

{ "key" : "ctrl喵" , "command" : "workbench.action.terminal.sendSequence" ,
"when" : "terminalFocus && !accessibilityModeEnabled && terminalShellType == 'pwsh'" ,
"args" : { "text" : " \u0016 " } },

This new keybinding will send the text representing Ctrl+V directly to PowerShell, which gets picked up by PSReadLine and handled properly.

Before:

After:

Theme: Sapphire (Dim)

Control double-click word selection

The new terminal.integrated.wordSeparators setting lets you customize the separator characters used to delimit a word when you double-click in the terminal.

The default separators are:

"terminal.integrated.wordSeparators" : " ()[]{}', \" `─"

Debugging Automatic debug configurations

Setting up debugging in VS Code can be a daunting task because a user has to create a new debug configuration (or at least modify a template to their needs). In our continuing effort to simplify the debugging experience, we have added a new feature that gives debug extension authors a means to analyze the current project and offer quality debug configurations automatically that do not require additional user configuration.

In a similar way to how build tasks are provided, the automatic debug configurations are grouped under the appropriate debugger (folder icon) in the Debug view's configuration dropdown and the Select and Start Debugging Quick Pick. Once the debugger is chosen, VS Code presents all the automatic configurations available. Selecting a configuration will start a new debugging session.

The following screen cast shows the feature for the new JavaScript debugger (in preview) and our educational Mock Debug:

The debug Quick Pick can be opened by typing 'debug ' (with a space) in Quick open (Ctrl+P) or by triggering the Debug: Select and Start Debugging command.

In the next milestone, we'll add UI so that an automatic debug configuration can be easily added to the launch.json for further configuration.

Tasks Disable faster Quick Pick

With version 1.44, we improved the task picker that shows when you run the Tasks: Run Task command by changing the layout and making it faster. However, the faster Quick Pick does make the task picker two levels deep depending on which task you want to run. If you want the previous UI, you can now disable the faster picker with the task.quickOpen.showAll setting.

Save on run

Previously, all dirty editors were always saved when a task is run. If you don't want to have your editors saved when you run a task, you can now configure that behavior with task.saveBeforeRun.

Languages TypeScript status bar entry enhancements

When you are focused on a TypeScript file, VS Code shows the current TypeScript version in the status bar:

Clicking on the version now brings up commands appropriate for the current TypeScript project:

Prompt users to switch to the workspace version of TypeScript

The new typescript.enablePromptUseWorkspaceTsdk setting brings up a prompt asking users if they want to switch to the workspace version of TypeScript:

To enable the prompt, include "typescript.enablePromptUseWorkspaceTsdk": true and typescript.tsdk as workspace settings for your project.