-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Maybe adjust behavior of useTabOnHangingIndent? #103
Comments
Not impossible to do, but it is more than a simple code change because we aren't inserting the ending bracket, we're just using A possible work around would be to delete the bracket that exists, and insert our own, adding a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is more of a question or comment than a feature request or bug report: What's the rationale for putting the cursor just before the closing bracket rather than just after, upon pressing Tab?
If I've got
and press Enter to get
and then type some elements, like
I would think that I am trying to get to
or perhaps even
as simply and easily as possible, but Tab actually gets me to
which is probably very rarely what I want. And by that time, the closing bracket is no longer considered "automatically inserted" by VS Code, and is thus not subject to the default typeover. (Setting
"editor.autoClosingOvertype": "always"
could help, but some people can't stomach that option.)I've been playing around with this a little bit, because it's close to allowing me to feel OK about letting VS Code autoclose brackets for me, but not quite there. And clearly most people don't seem to have any problem with the current VS Code behavior, with or without
useTabOnHangingIndent
.The text was updated successfully, but these errors were encountered: