The previous binding to follow had ergonomics issues for the frequency that I think we'll want to use it. It would also conflict with the sub-word selection binding.
Now that moving the cursor etc unfollows, I don't think we need the follow binding.
Nathan Sobo
created
da15669
Merge pull request #656 from zed-industries/add-editor-lifetime-events
Click to expand commit body
Add editor lifetime events
Nathan Sobo
created
d24bd6f
Account for pending selections when calling `Editor::refresh_selections`
Antonio Scandurra
created
3298529
Fix global nested event test after turning subscriptions into effects
Antonio Scandurra
created
7acde40
Merge pull request #655 from zed-industries/add-editor-selection-helpers
ffaf409
Forget last pane's leader when such pane is removed
Click to expand commit body
This is just a memory optimization and doesn't cause any observable
change in behavior.
Antonio Scandurra
created
5dc3626
Reflect leader's view state when recycling existing local editors
Antonio Scandurra
created
34e5a1f
Always render local selections on top of remote ones
Antonio Scandurra
created
7d566ce
Follow last collaborator or the next one via `cmd-alt-shift-f`
Antonio Scandurra
created
67dbc31
Stop following when activating a different item on the follower pane
Antonio Scandurra
created
3117554
Automatically unfollow when editing, scrolling or changing selections
Antonio Scandurra
created
c550fc3
WIP - Start work on unfollowing automatically
Max Brunsfeld
created
1728551
Always mirror the leader's selections when following
Max Brunsfeld
created
ee3e604
Make boundary-finding methods wrap across newlines
Click to expand commit body
This requires word and subword methods to explicitly acknowledge that they want to stop at newlines, which I think actually increases clarity. It makes the boundary finding method more general and useful for external callers such as the forthcoming vim crate.
This is just a character, and so it seems clearer to refer to it specifically when we want to know if a character is a newline. There was only one case where we relied on Newline being different from Whitespace, and we special-cased that instance. Changing this actually makes us match the behavior of VS Code when double-clicking runs of multiple newlines.
/cc @as-cii
Co-Authored-By: Keith Simmons <keith@the-simmons.net>
Nathan Sobo
and
Keith Simmons
created
baeb7d2
Clarify word movement function names and improve test coverage
Click to expand commit body
Co-Authored-By: Keith Simmons <keith@the-simmons.net>
Nathan Sobo
and
Keith Simmons
created
06cd9ac
Match the leader's last selection when unfollowing
Click to expand commit body
Co-Authored-By: Antonio Scandurra <me@as-cii.com>
Max Brunsfeld
and
Antonio Scandurra
created
3e0bc97
Avoid infinite loop when collaborators follow each other
Click to expand commit body
Co-Authored-By: Antonio Scandurra <me@as-cii.com>
Max Brunsfeld
and
Antonio Scandurra
created
05ddd26
Merge pull request #648 from zed-industries/update-fonts-to-1-2-1