Add config to use old brackets/quotes overtyping

[usernamehw]

#37315

It's a breaking change. And very noticeable at that.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Test new overtyping in auto closing pairs (#78118)

[alexdima]

@usernamehw I've changed the editor to overtype only quotes and parens auto-inserted by the editor. Would you like to have the old behaviour of overtyping even characters that were not auto-inserted or have you maybe run into a special case in HTML/css/etc.?

[usernamehw]

No special cases. Old behavior.

[haymez]

Obviously a lot of people requested the new behavior but I would agree with @usernamehw in that the new behavior is quite jarring and I'm a little surprised that the default behavior changed instead of a setting being added to support the new behavior for those that wanted to switch. Having the editor sometimes swallow closing tags but other times not is kinda frustrating although I can see the reasoning behind it.

[patrickodacre]

I miss the old behavior. I'm constantly deleting extra characters now =\ I'll be rolling back my version until this feature is added back. Thanks for all the hard work, folks!

[larsnystrom]

The problem is that not all auto-inserted brackets are considered auto-inserted in the new implementation. If I write (PHP) array_key_l and use tab to auto-expand to array_key_last() the editor inserts the parenthesis for the function and puts the cursor in between them, but typing ) won't overtype the ending parenthesis, since I auto-completed the entire function name and not just the parenthesis. The closing parenthesis is not considered auto-inserted because it was inserted as part of the function autocompletion feature and not the autoClosingBrackets feature.

This means I have to keep track of how the brackets was auto-inserted in order to know when typing a closing bracket will overwrite the auto-inserted one, or just insert a new character.

Edit: This could possibly be considered a bug, and not part of this feature request.

[gjsjohnmurray]

The problem is that not all auto-inserted brackets are considered auto-inserted in the new implementation.

@larsnystrom this is #78975

[tabennett]

This is making this editor nearly unusable for me. The old behavior is consistent with previous editors I was using (atom, sublime text) before coming to VS Code. Pretty frustrating/jarring to have BC changes like this come though.