Currently, remove-matching-brackets acts as a normal backspace if you have a selection. Instead, it should act as remove-brackets-from-selection does. Furthermore, remove-brackets-from-selection (and the new remove-matching-brackets) should look just out outside of the selection for brackets if they're not found within the selection. This is a lot more usable and plays nicely with select-inside-brackets.
If this is done, remove-matching-brackets could theoretically be removed, and the convenient ctrl-backspace binding can be a swiss army knife.
Some nice usages:
ctrl-cmd-m ctrl-backspace ( to replace existing brackets with parenthesis (very similar to cs[( in vim-surround).
Currently,
remove-matching-brackets
acts as a normal backspace if you have a selection. Instead, it should act asremove-brackets-from-selection
does. Furthermore,remove-brackets-from-selection
(and the newremove-matching-brackets
) should look just out outside of the selection for brackets if they're not found within the selection. This is a lot more usable and plays nicely withselect-inside-brackets
.If this is done,
remove-matching-brackets
could theoretically be removed, and the convenient ctrl-backspace binding can be a swiss army knife.Some nice usages:
ctrl-cmd-m ctrl-backspace (
to replace existing brackets with parenthesis (very similar tocs[(
in vim-surround).