Disable closing bracket swallowing?

This question already has answers here:

I received a solution from github of vscode project. It works for me. Edit your keybindings.json add the text below:

{
"key": "]",
"command": "editor.action.insertSnippet",
"when": "editorTextFocus",
"args": {
    "snippet": "]"
}
},
{
"key": "Shift+]",
"command": "editor.action.insertSnippet",
"when": "editorTextFocus",
"args": {
    "snippet": "}"
}
},
{
"key": "Shift+0",
"command": "editor.action.insertSnippet",
"when": "editorTextFocus",
"args": {
    "snippet": ")"
}
}

Notice: "Shift+0" for en keyboard (, edit it for your keyboard layout.

How to stop atom from auto closing and swallowing braces and quotes, It's just enabled by default. To disable or tweak the behavior, you can go to Settings -> Packages -> bracket-matcher . I never have found auto closing of tags helpful, that is, until I starting get used to the way Atom handles it. When you have the cursor in front of a ], ) or } and you type that character, instead of inserting it vscode just moves past that character, producing ]*cursor here* instead of ]*cursor here*]. Bec

Add config to use old brackets/quotes overtyping � Issue #78833 , Having the editor sometimes swallow closing tags but other times not is Add setting to turn off bracket-swallowing while autoclose is active #� There’s also a bug in all versions of Sublime regarding this feature, where program “silently swallows” closing bracket, leaving user unaware of situation. Imagine the amount of anger which occurs when you’re a step away from testing and you hit “ close bracket ” key to close function or some other inline element, save document and

TL;DR: currently it is not possible to disable this annoying feature.

I'v asked the same question here.

There is an open issue in their repo.

can't disable autoclose brackets, What I absolutely loathe about the Auto-Close feature is that it not only generates matching parentheses but sometimes swallows a closing� Probably will be ok: As long as the metal bracket doesn't go down the lung, the gastrointestinal tract will clear the swallowed bracket. However of you experience any wheezing or chest pain, go to the emergency immediately.

How to stop VS Code from eating my brackets? : vscode, let "|" represent my cursor, if I type a closing bracket ")" it won't give me a bracket, it will just do this To disable rendering the characters, set "editor.minimap. Most of it is really helpful, but some things are extremely annoing and even hard to find in the settings. One of these things is the automatic closing of brackets, curly braces, quotes and things like that. I hate these type of functionality and this is one of the first things I disable in every IDE so far.

How to Turn Off Autocomplete For Brackets and Quotes in Sublime , Turn off auto-closing for regular, square and curly brackets as well as quotes and double quotes (also fix closing bracket swallowing bug):. On Jupyter 4.0.6 on Kubuntu 14.04, with any of the config.js shown below, autoclose brackets won't stop autoclosing. This has to be the most annoying 'helpful feature', especially since its idea of where to autoclose is almost always wro

ST3 eats right parentheses, brackets, quotes, ST3 has an incredibly annoying habit of eating right parentheses, and is meant to prevent to accidentally add extra closing brackets, but it's a� The three components to autoClosingBrackets make sense when typing new code, but when there is a missing closing bracket for whatever reason and the cursor is moved to the left of an existing closing bracket by arrow keys or a mouse, the cursor moving past the existing closing bracket is frustrating.

Comments

Can you provide an example of what you are referring to?
@ifconfig 1. Type ) 2. place the cursor right before the ) 3. Type ) again. 4. Result -> ) with cursor after the ). Desired Result -> )) with cursor in the middle. Don't know how to put it more plainly than that.
The answer is (now) yes, you can get the behavior you want. Without any clever keybindings or other tricks.
I wish I could buy you a beer for this answer!
Great answer that fixes the problem as stated, but it really breaks the autoClosingBrackets feature because now when you touch type something like () {};, you end up with `() {};})", which is really not what you want.
@robocat - It may not be what you want, but I think some people actually are fine with that. Not that they really want extra closing brackets at the end, but some people are actually used to typing a left bracket, then pressing right arrow or End to get past the automatically generated right bracket. It's their workflow and what makes sense to them. Anyway, it may soon be moot because they are working on more sophisticated bracket overtyping behavior.
@john-y That link is fantastic news, it certainly looks like it will fix this properly. Cheers
I hate the last functionality you mentioned - the one about enclosing selected text instead of replacing it with typed bracket character. It's a shame you need to disable these features all at once, or none at all.