Kakoune vs Leo Editor

Kakoune first started as a rewrite from scratch of vim, but then ended up being another text editor altogether. So it's inspired in a lot of ways from vim.

It follows the UNIX philosophy by doing one thing well (text editing) and interfaces nicely with other CLI tools.

Kakoune works on selections, which are oriented, inclusive range of characters, selections have an anchor and a cursor character. Most commands move both of them, except when extending selection where the anchor character stays fixed and the cursor one moves around.

Kakoune provides a very expressive set of commands, including various objects selection (paragraph, blocks, words), alignment support, conditional selection filtering...

This set of command is expressive enough to implement all the provided auto indentation logic.

A helper pops up when typing commands.

Some keys select, other keys operate on the selections. Shift is used to extend the selection, alt is used for alternative behavior, e.g. reverse the search direction. No inconsistencies like Y which means yy and not y$ in Vim.

With outlines functions and classes can be arranged and grouped with their logical neighbours, even nested. Whole branch hierarchies can be expanded and collapsed in a single key stroke, or moved from this spot to that, as best fits the thinking or troubleshooting of the day. Outline trees make navigation across broadly different areas an effortless exercise. See your whole project in a single view, across any number of external files and modules.

All Leo editor commands are available in a command bar, called a "mini-buffer", that feature tab-completion and command history. For example "Find all nodes containing phrase '...', clone them, and paste in a new tree" is a simple alt-x, clone-find-flattened (or cff) away. As is toggle-split-direction, expand/contract-log-pane and execute-script.

Leo's unique concept of 'clones' means you can re-arrange sections of an external file to suit your way of thinking or tacking a specific issue without changing the organization of the source. This makes it a great tool for studying code from others, and perhaps contributing back to them without changing your or their preferred arrangement methods.