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
This also changes the structure of the follow state back to be per-pane. This
is because we can't share the same view state across different panes for
a couple of reasons:
- Rendering the same view in N different panes is almost always not something
that we want due to global state such as focus.
- If we allowed it and a user followed the same person in two different panes,
there would be no way of unfollowing in one pane without also unfollowing in
the other.
Antonio Scandurra
created
a2dbebd
Hide cursor both locally and remotely when following
Antonio Scandurra
created
c03eec0
Merge pull request #647 from zed-industries/fix-reopening-project-items
Click to expand commit body
Pass project entry id to Pane when opening a project item
Nathan Sobo
created
7cb8935
Pass project entry id to Pane when opening a project items
Click to expand commit body
This fixes an oversight where we were failing to associate project items with their project entry ids, which broke the logic that prevented the same project entry from being opened twice in the same pane.
Nathan Sobo
created
0e920ad
Unset follower's scroll anchor when editor is scrolled all the way up
5702737
Start work on an integration test for following
Max Brunsfeld
created
845457e
Always read project entry id from workspace::Item
Click to expand commit body
We cannot store a workspace item's project entry id separately,
since buffers' entry ids can change (for example when doing
a *save as*).
Co-Authored-By: Antonio Scandurra <me@as-cii.com>