sl0ppij.git/Cargo.toml, branch main

sl0p: tag fork builds as 0.45.0+sl0p1

2026-08-08T19:24:00Z

`zellij --version` was identical to upstream, so there was no way to tell a fork binary from a stock one. Uses BUILD METADATA (+sl0p1) rather than a prerelease (-sl0p1): cargo ignores build metadata when matching version requirements, so the intra-workspace `zellij-utils = "0.45.0"` dependencies still resolve. The prerelease form was tried first and fails to resolve - it would require updating every member manifest to depend on the exact prerelease. Checked against the places VERSION is actually consumed: - shared::version_number() yields 4500 for both 0.45.0 and 0.45.0+sl0p1, so terminal version reporting is byte-identical, and still orders below 0.46.0. - client/server compatibility keys off CLIENT_SERVER_CONTRACT_VERSION, not this, so existing sessions are unaffected. - ZELLIJ_PLUGIN_ARTIFACT_DIR is keyed by VERSION, so the bundled wasm plugins are recompiled once on first run after a bump. One-time, harmless. Baselines held: zellij-server 1421/30, zellij-utils 435/5.

sl0p: add fastdev build profile + SPEED.md (60x faster iteration)

2026-08-08T18:46:53Z

Building this fork for local use took ~3 minutes per one-line change: [profile.release] sets lto = true and codegen-units = 1, so every rebuild redid whole-program optimization on a single core. That is right for a shipped artifact and pure waste for a binary we just want to look at in a terminal - zellij is bound on a human, not on codegen. [profile.fastdev] inherits release, keeps opt-level 3, drops LTO, uses 16 codegen units and keeps the incremental cache: cargo build --profile fastdev -p zellij ~2.8s incremental (was ~3min) [profile.release] is deliberately untouched, so shipping/benchmarking builds are unchanged. .fastfeedback/SPEED.md records the narrow commands, measured timings, the deploy loop, and - importantly - the PRE-EXISTING test failure baselines (30 in zellij-server, 5 in zellij-utils) so a future session does not waste time chasing failures it did not cause. Rejected: the gold linker (rustc warns it is deprecated with known Rust bugs) and clang+lld (no lld binary installed). Dropping LTO removed the dominant cost anyway.

fix(build): remove manpage, honor CARGO_TARGET_DIR, add cargo argument passthrough, remove clippy (#5426)

2026-07-30T14:50:12Z

* fix(build): remove manpage, honor CARGO_TARGET_DIR, add cargo argument passthrough, remove clippy * add pr

More dependency upgrades for debian (#5421)

2026-07-29T15:08:08Z

* upgrade insta, rand, sha2, strum, thiserror, tokio-tungstenite, toml, which; drop unused semver and typetag * upgrade sysinfo to 0.39.5, bump toolchain (msrv) to 1.95.0 * remote legacy yaml config converter and thus drop serde_yaml * upgrade unicode-width to 0.2.2 * fix(tests): run ipc roundtrip test on a larger stack

Dep upgrades for debian (#5420)

2026-07-28T10:05:38Z

* chore(deps): upgrade base64 0.22, colored 3.1, crossterm 0.29, dialoguer 0.11, directories 6.0, highway 1.2, prost 0.12.6, strip-ansi-escapes 0.2.1, suggest 0.5.1 * chore(deps): upgrade miette 7.6, nix 0.30, notify 8.2, notify-debouncer-full 0.5 * vte 0.15 * clap 4.6 * workspaceify plugin deps * don't send empty fs watch events

Switch from the unmaintained daemonize crate to a maintained fork (#4512)

2026-07-27T11:08:50Z

* Switch from the unmaintained daemonize crate to a maintained fork c.f. https://rustsec.org/advisories/RUSTSEC-2025-0069.html * add pr --------- Co-authored-by: Aram Drevekenin

Reduce compilation time (#5321)

2026-06-30T19:18:58Z

* perf: speed up dev builds * rustfmt * fix flake

chore: new test infra (#5269)

2026-06-16T13:44:22Z

* initial implementation * refactoring and cleanups * port basic e2e tests * fix tab rotation * migrate client and mouse tests * migrate the rest of the tests * remove old e2e tests * rustfmt * add e2e note * fix stale test * fix: cross platform locking/cleanup * fix: change mode race discovered by tests * rustfmt * fix: attach/detach race in tests * fix plugin test assertion * add pr

Mobile layout (#5241)

2026-06-10T14:50:55Z

* phase 2+3 * initial mobile plugin (phases 4 + 5 + 6) * some bugfixes * implement stage 7 * mobile interface improvements * improve mobile pane/tab picker * more ui improvements and fixes * various mobile fixes * some mobile fixes * mobile keyboard triggering fix * some cleanups * initial plugin keyboard implementation * improve keyboard hit zones * improve keyboard * pinch resize * pinching fixes * implement scrolling + panning * initial keyboard resizing * fix: mobile first render issues * keyboard responsiveness * fix some issues with the keyboard * implement fit * fix mobile scrolling * add tilde cell to compact * improve mobile keyboard * fix starting mobile terminal font to natural keyboard size * fix mobile resize blank screen flash * shadow focus for mobile * more keyboard fixes * improve mobile status bar * fix: render plugins to mobile clients * allow opening new panes/tabs from the mobile plugin * allow configuring * fix dot slash * improve mobile native soft keyboard interaction * switch to native keyboard - initial implementation * dirty hacks, but phone keyboard works now * adjust keyboard help strip * fix cursor in mobile * fix keyboard and help line * rename keyboard to modifier bar * allow starting new session * make clicking session name bring us to new session menu * allow switching to desktop from the mobile ui * mobile welcome screen initial implementation * mobile welcome screen fixes * various welcome screen fixes * more mobile fixes * moar mobile fixes * mobile ui redesign * fix: swallowed backspace bug * switch session screen improvement * touch up some interfaces * refactor: move mobile state to own struct * refactor: move fit resizing to the server * remove dead flash code * some cleanups * refactor: clear fit on close * refactor: improve fit api * refactor: pane sync functions * refactor: mouse * refactor: break into modules * some cleanups for the sessions screen * fix scrolling and other stuff * refactor: sessions screen * refactor: panes screen * refactor: new session screen * refactor: menu screen * refactor: render * cleanups * refactor: plugin structure * remove unused welcome screen path * Rename api * refactor input.js * cleanup useless comments * fit/mobile refactoring * take out the garbage * remove more comments * remove mobile flash on startup/attach * fix: various mobile startup issues * fix space bugs * cleanup * rustfmt * fix windows build * adjust modifier bar ui * add pr

fix(windows): bump windows-sys to 0.59 (#5139)

2026-05-06T15:02:10Z

The workspace `windows-sys` constraint was pinned to 0.52 while the Windows source uses APIs and namespaces from 0.59 (e.g. WriteFile in Win32::Storage::FileSystem). CI built fine because Cargo.lock pinned 0.59, but downstream `cargo install`/`cargo binstall` did fresh resolution and selected 0.52, breaking the build for users on Windows. Align the manifest with the code: - Bump workspace dep `windows-sys` from 0.52 to 0.59. - HANDLE is now `*mut c_void` instead of `isize`: replace `handle == 0` / `!= 0` with `is_null()`, initialise HANDLE locals with `std::ptr::null_mut()`, and pass `null_mut()` as the hTemplateFile argument to CreateFileW. - Pass the process HANDLE through the exit-monitor thread as `usize` (raw pointers are not Send; OS handles are safe to use cross-thread). - Note: HPCON is still `isize` in 0.59, so its zero-init is unchanged.