New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete matching closing bracket even if it is lower in the file #127101
Comments
(Experimental duplicate detection) |
What is your |
@ArturoDent It seems that this setting doesn’t work as expected. Just try to move the bracket to another line. Then move the cursor back to opening one and you will see that it won’t delete the closing bracket. |
bump :) |
@dimaxiton1 What are the steps to reproduce the problem? If I open a blank TS file in a default VS Code installation and type |
Sorry for the latency here. Here is some demos on clean Insiders build: Default VS Code installation (before setting the So my proposal here is to make VS Code always remove the closing bracket out of the box. This should better align with other editors (WebStorm, Xcode etc). Also I missing a setting that would always remove the closing bracket (even if it on another line). This should better align with WebStorm defaults. I hope I made it clear. |
Thank you @zardoy for the extra explanation. On the first GIF, when pressing On the second GIF, we never implemented something like that. i.e. delete matching closing bracket at distance. We only ever implemented deleting the matching closing bracket when the brackets touch. We can use this issue to track this feature request. |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
[] () {}
brackets. Try to close the opening one.Please make the same behavior that is using WebStorm: to always close any matching bracket, just because it is extremely convenient. Like seriously, I don't have time to close the matching bracket, especially in very complicated TS file, where I have multiple interfaces. Please make that behaviour to work out of the box. I believe that the future in your hands, you're building the amazing IDE, thank you VSCode guys!
The text was updated successfully, but these errors were encountered: