The development team responsible for the source code editor at Microsoft has released version 1.58 of Visual Studio Code (VS Code). The June update includes the ability to create terminals in the editor or move them to the editor area. The development team is also expanding the restricted mode settings for potentially untrusted code.
Create and move terminals in the editor
The June update allows terminals to be created and moved in or into the editor area. This results in the possibility of a multi-dimensional grid layout that remains independent of the panel state and is visible.
There are several options for using terminals in the editor area: Developers can use the command Create Terminal in Editor Area use to create. A terminal can be dragged and dropped from the tab list into the editor. In addition, developers can use the command Move Terminal into Editor Area run while a terminal is in focus. The tab’s context menu also offers Terminal the option Move into Editor Area. In addition, the update offers the setting option
terminal.integrated.defaultLocation on the editor so that newly created terminals are routed to the editor area by default.
With the May update of VS Code, the development team behind the editor Workspace Trust introduced a restricted mode for potentially untrusted code. With Workspace Trust developers can choose whether to trust the code in a folder. If you want to view unknown code from potentially untrustworthy sources risk-free, you can access it in
Restricted Mode to edit. In this case, Visual Studio Code prevents any automatic execution: Tasks are deactivated, as is debugging. In addition, the source code editor restricts the extensions and workspace settings in this case.
A month later, the development team is now responding to customer feedback and fixing one or two problems with the June update. For example, the update for adjusting the user settings for the Workspace Trust a new way of action Config your Settings in the header of the editor. With this action the after
@tag:workspaceTrust filtered settings editor called.
In addition, the update introduces a new setting for the configuration of the banner. Users can configure the banner that indicates that the current window is in restricted mode. In this way, the banner can be deactivated after users have contacted Workspace Trust and no longer need a reminder that they are working in restricted mode.
The update offers a variety of other innovations. More information about the June update of the source code editor can be found in the post on the Visual Studio Code blog.