AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Hexcells off screen1/3/2023 ![]() ![]()
Until today, the VS Code debugger had no standard way of showing that a file in the editor could be easily debugged with just a click of a button. If you run into any problems, please open an issue! Single file debugging You should not need to change any settings or launch configurations to take advantage of the new debugger. If you skipped the "Preview Features" section of the last few VS Code changelogs, you can catch up on the what's new section of the debugger README. Our new JavaScript debugger, after being the default debugger on Insiders last month, is now the default debugger for JavaScript (Node.js and Chrome) in VS Code. The modifiers can also be stacked - for example, \u\u\u$1 will uppercase the first three characters of the group, or \l\U$1 will lowercase the first character, and uppercase the rest.Ĭurrently, these are only supported in the editor's Find control, and not in global Find in Files. This is done with the modifiers \u\U\l\L, where \u and \l will upper/lowercase a single character, and \U and \L will upper/lowercase the rest of the matching group. VS Code now supports changing the case of regex matching groups while doing a find/replace in the editor. The previously existing setting can now be toggled at runtime without forcing you to reload the workbench. To go back to the old behavior, set the value back to 0. The setting has been updated to have a default value of 1 instead of 0, meaning one context line will be shown before and after each result line in the Search editor. The command is not bound to any keyboard shortcut by default, but you can add your own keybinding: New Search editor context default This can be helpful if you want to select multiple files from a list, such as the File Explorer, without having focus go to the file editor. There is a new command, lectAndPreserveFocus, which lets you select an item from a list, while keeping focus in that list. Extension authors can use this functionality to increase the visibility of these kinds of settings. Now, you can edit non-nested object settings from the Settings editor. Workbench Edit object settings from the Settings editorīefore, the Settings editor could only be used to edit the settings of primitive types, like strings and booleans, and you needed to edit settings.json directly for more complicated settings types.
0 Comments
Read More
Leave a Reply. |