Fix consecutive cursors being filtered out #3823
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When pasting from the clipboard (or inserting) with multiple cursors, cursors that are directly next to each other are filtered out.
The reason for this is that
EventHandler.Replacetriggers two separate events to mimic the replacement. These two events are processed sequentially inDoTextEvent, which means that these two consecutive cursors have the same position afterTextEventRemove. The second eventTextEventInsert, can no longer distinguish between them, andBuffer.MergeCursorsfilters out one cursor later.How to reproduce:
Create 2 cursors with selections directly next to each other. Each cursor selects one
c.Insert any character, e.g.
xor paste your clipboard.Expectation:
Actual behavior:
So, one cursor gets lost.
The last commit (
Always stop Undo(), Redo() after TextEventReplace) is totally subjective and up for debate. For me personally it feels much better to have more control forTextEventReplaceundos/redos. Let me know what you think.