Files
sandroid 58849026ec helix: Honor use_system_clipboard (#66906)
## Summary

## What problem does this solve, how, and why does this change matter?

Ensures helix mode honors the the configured `use_system_clipboard`
instead of always ignoring it and acting as if the value was
`UseSystemClipboard::Never`.

To be honest, I'm a bit confused why #55455 decided that Helix mode
should deliberately ignore the configured setting, when the desired
behavior ("not clobbering the system clipboard") is already available
with `Never`, maybe @SrGaabriel can shed some light on this? I find the
feature to always copy/paste to/from the system clipboard super handy,
especially when using in combination with a clipboard manager.

closes #66782

## Testing

Enable helix mode. When `use_system_clipboard` is set to `Always` or
`OnYank`, `y` and `p` yank and paste from/to the system clipboard. When
`use_system_clipboard` is set to `Never`, `y` and `p` yank and paste
from/to the internal register.

I mostly duplicated the tests added in #55455 and run them against the
two different scenarios: `Always` and `Never`. For the tests targeting
the specific registers, I removed the assumption about the system
clipboard because IMO this is not what these tests should test. Let me
know if that's fine or if I should iterate on that.

## Self-review

- [X] I've reviewed my diff for quality, security, reliability, and
performance.
- [X] UI changes follow the
[checklist](https://zed.dev/docs/development/ui-checklist).
- [X] Tests cover the new or changed behavior.

Release Notes:

- Fixed Helix mode ignoring the `vim.use_system_clipboard` setting.
Yank, delete and paste in Helix mode use the system clipboard by default
again, as they did before 1.28 . If you wish to keep the 1.28 behavior,
set `"vim": { "use_system_clipboard": "never" }` to keep using the
internal register.
2026-11-17 16:48:24 +00:00
..
…

This contains the code for Zed's Vim emulation mode.

Vim mode in Zed is supposed to primarily "do what you expect": it mostly tries to copy vim exactly, but will use Zed-specific functionality when available to make things smoother. This means Zed will never be 100% vim compatible, but should be 100% vim familiar!

The backlog is maintained in the #vim channel notes.

Testing against Neovim

If you are making a change to make Zed's behavior more closely match vim/nvim, you can create a test using the NeovimBackedTestContext.

For example, the following test checks that Zed and Neovim have the same behavior when running * in visual mode:

#[gpui::test]
async fn test_visual_star_hash(cx: &mut gpui::TestAppContext) {
    let mut cx = NeovimBackedTestContext::new(cx).await;

    cx.set_shared_state("ˇa.c. abcd a.c. abcd").await;
    cx.simulate_shared_keystrokes(["v", "3", "l", "*"]).await;
    cx.assert_shared_state("a.c. abcd ˇa.c. abcd").await;
}

To keep CI runs fast, by default the neovim tests use a cached JSON file that records what neovim did (see crates/vim/test_data), but while developing this test you'll need to run it with the neovim flag enabled:

cargo test -p vim --features neovim test_visual_star_hash

This will run your keystrokes against a headless neovim and cache the results in the test_data directory. Note that neovim must be installed and reachable on your $PATH in order to run the feature.

Testing zed-only behavior

Zed does more than vim/neovim in their default modes. The VimTestContext can be used instead. This lets you test integration with the language server and other parts of zed's UI that don't have a NeoVim equivalent.