| Filename | Latest commit message | Latest commit date |
|---|---|---|
ebbc7743e7
Move the whole workspace to Rust 1.97 (from 1.96) and bump ~120 dependencies to their latest major versions. The full 230-crate workspace compiles, joule_core's 182 tests pass, the release daemon builds, and LFM2 still loads + runs. API adaptations for the major bumps: - rand 0.10: rand_core renamed RngCore->Rng and moved the sugar (random_range, from_os_rng) onto RngExt / removed it — updated call sites + imports. - yawc 0.3: FrameView->Frame with accessor methods; client socket is TcpWebSocket. - sqlx 0.9 / heed 0.22 / axum 0.8: renamed/removed cargo features. - core-video 0.6: create_texture_from_image takes &CVImageBuffer; convert via TCVImageBuffer::as_image_buffer. - prost: Message no longer implies Debug — added the bound. - cargo_toml 1.0: lints is now Inheritable<LintGroups> (Inherited == workspace). - ed25519-dalek, core-text, core-graphics, cpal: pinned to the versions the git-forked deps (open-standands receipts, zed-font-kit, rodio) are built against — a split breaks shared SigningKey/CTFont/CGFont/Device types. Deliberate holds (their own migration, not a blind sweep): - livekit/libwebrtc/webrtc-sys/coreaudio-rs: the real-time A/V stack, pinned to Zed's livekit-rust-sdks fork; latest breaks livekit_client deeply. - wasmtime 36 + wit-bindgen 0.41: the extension component-model ABI, tied to the pinned zed:extension WIT worlds. - brush-parser 0.3: 0.4 reshapes the AST on the command-safety allow-gate path. - runtimelib/nbformat/jupyter-protocol 1.x: the REPL Jupyter stack moves majors together. Also: unlisted Zed's hosted-collab SERVER (crates/collab) from the workspace — a leaf binary nothing depends on, whose pinned sea-orm/sqlx chain blocked the upgrade; source stays on disk. All open-standards git deps repointed to the forge URL and bumped to c4b536cf (320fa1e + score_binary). Co-Authored-By: Claude Opus 4.8 <[email protected]> |
||
| .. | ||
| src | ||
| test_data | ||
| Cargo.toml | ||
| LICENSE-GPL | ||
| README.md | ||
This contains the code for Joule's Vim emulation mode.
Vim mode in Joule is supposed to primarily "do what you expect": it mostly tries to copy vim exactly, but will use Joule-specific functionality when available to make things smoother. This means Joule 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 Joule's behavior more closely match vim/nvim, you can create a test using the NeovimBackedTestContext.
For example, the following test checks that Joule 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
Joule 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.