Open untitled buffers via the `Project`

Use LSP range formatting when document formatting is not available

This allows the registration of such buffers in the project, which is necessary
to correctly support `::save_buffer_as` and opens the door to sharing untitled
buffers with guests in the future.

Note that, for now, this disallows guests to create untitled buffers in the
current window and will create a new window instead. This is because we don't
yet have a global way of allocating a buffer's remote id (nor a way of saving
such buffers in the host's worktree) and we instead rely on the local model ID,
which could clash with the host's buffer IDs.

I think we should revisit this once guests can share their untitled buffers
with the host and other remote peers, as well as once we start keying
operations by entry id.

Grow worktrees monotonically when sharing and move most messages to the background

Avoid infinite loop when a language server fails to start

We don't use them, and they add a lot of noise to the test output
when running all tests in the workspace.

Add basic JSON support

The feature doesn't work yet because the JSON language server
only supports *range* formatting, not document formatting.
We need to adjust our code to inspect the server's capabilities
and send range formatting requests instead when needed.

We're going to hold off on doing this right now, because it
will create merge conflicts with the `preserve-worktrees`
branch (#525)

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Co-Authored-By: Nathan Sobo <nathan@zed.dev>
Co-Authored-By: Max Brunsfeld <max@zed.dev>

This accidentally regressed in 53327e2.

This could happen because there was a pause between creating the worktree
and adding it to the list of tracked local worktrees, and so we might end
up adding the same worktree twice when calling `create_local_worktree` in
rapid succession.

- On the host, ensure that only one worktree can exist for a given absolute
path. Asserting about buffers was cool but I think should be tackled in the
context of leaning more on entry ids for collaboration (vs. buffer ids).
- On the guest, ensure that all the opened buffers don't contain deferred
operations.

Co-Authored-By: Max Brunsfeld <max@zed.dev>

Co-Authored-By: Max Brunsfeld <max@zed.dev>
Co-Authored-By: Nathan Sobo <nathan@zed.dev>

Co-Authored-By: Max Brunsfeld <max@zed.dev>

Don't insert input into editors when control or command keys are held

This is a follow-up to #475

Make pane active when activating one of its items

This is better for caching and, thus, yields faster CI runs.

Project-wide search