Surround delete breaks the select -> action model
#10238
Replies: 4 comments
I agree I think this is better covered by #2413. |
|
Selections are enough for visual confirmation IMO. I also wouldn't mind using #2413 for surround delete, however #2413 would not work well if you want to surround delete multiple times. Example: |
|
This one caught me off-guard. I expected this to work differently—more like |
|
This also caught me off-guard. I also expected to be able to select the surrounding delimiters and then I could decide to delete or change them. Something like #9483. It seems that Helix has decided against this behavior? I think the selection -> action model is really strong and should extend to something this basic as well. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In helix the
surround deletecommandmddoesn't respect selections, the action needs another key to specify which character to delete. This breaks theselect -> actionmodel since I can't visually confirm what's being deleted.I propose
helixto add asurround delete selection, which simply deletes the first and last characters of current selections.Example:
All reactions