Kakoune code editor introduces modal editing with multiple selections as core interaction model

Kakoune reimagines text editing by making multiple selections the default interaction paradigm. Unlike traditional editors where selections are secondary to cursor movement, Kakoune treats them as first-class objects with built-in primitives for regex matching, filtering, splitting, and alignment. This design aims to minimize repetitive keystrokes by allowing engineers to apply transformations to multiple regions of text simultaneously. The trade-off is a learning curve for users accustomed to single-cursor workflows, particularly in modal editing where commands operate on selections rather than individual characters or lines.

The editor’s orthogonal design means features are composable rather than nested in menus or modes. For example, selections can be rotated, case-swapped, or indented without leaving the primary editing context. This reduces cognitive overhead for complex edits but requires users to internalize a new set of primitives. The lack of a plugin system (replaced by macros and hooks) simplifies maintenance but may limit integration with external tools or language servers. Engineers evaluating Kakoune will need to weigh its built-in capabilities against the extensibility of alternatives like Vim or VS Code.

Kakoune’s client-server architecture enables real-time collaborative editing without third-party services. All editor windows act as clients connected to a shared session, allowing simultaneous modifications to the same file. This is distinct from screen-sharing or pair-programming plugins, as it operates at the editor level. The integration with tmux further extends this model to terminal-only workflows. However, the architecture may introduce latency or synchronization issues in high-latency environments, and there’s no built-in conflict resolution for overlapping edits. Teams adopting Kakoune for collaboration will need to establish conventions for concurrent editing.

The project’s active development and community support suggest ongoing refinement, but its niche focus may limit adoption. While Kakoune’s design reduces reliance on plugins, it also means fewer pre-built integrations for modern toolchains (e.g., debuggers, linters). Engineers considering a switch will need to assess whether its orthogonal primitives and multiple-selection model justify retraining, particularly in environments where tooling compatibility is critical. The absence of a plugin ecosystem could be a strength for stability or a limitation for extensibility, depending on the use case.