symflower-kakoune
golf
Our great sponsors
symflower-kakoune | golf | |
---|---|---|
1 | 3 | |
13 | 118 | |
- | - | |
0.0 | 9.3 | |
over 1 year ago | 29 days ago | |
KakouneScript | Shell | |
MIT License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
symflower-kakoune
-
Kakoune Code Editor
At Symflower we do, one of us has it as its main editor and it looks extremely productive. As a former VIM hardcore user i enjoy the pair programming sessions. I guess these sessions must feel the same way when a non-VIM user watches a VIM hardcore user.
We even have an extension for Symflower https://github.com/symflower/symflower-kakoune that is how much we appreciate Kakoune.
golf
-
Why Kakoune
I'd probably use Helix if it had 1:1 Kakoune keybindings. Or even Vim bindings.
Vim bindings are not the most consistent, but they are ubiquitous. Every program that offers Vim mode has very similar keymap. If modal text editor deviates from them, it better be for good reason.
Kakoune bindings are very different from Vim, but they are provably and objectively [1] better, so that's fine. They are also more consistent and there is a clear idea behind the whole design. It's written down in documentation. You might prefer Vim or Emacs, but at least you can see that changes from well known Vim scheme are not made at whim.
Helix keymap feels like it was improvised without any thought behind it. „Let's take Kakoune binds and add back visual mode cuz I feel like it.” Currently, they are designed by committee in this GitHub issue[2]. I don't see any design notes and explanations why should I spend time learning Helix keymap.
[1]: https://github.com/mawww/golf
-
Is there objective data on the "most efficient" modal editor?
People claim that their new(er) modal text editor is better/faster/requires fewer keystrokes than vi/vim/neovim, but I have yet to see some clear, objective, concrete data to back these claims up (like a benchmark of the editors for the same tasks). Is there anything of this sort? I know there's this, but it's only about kakoune/vim and it seems a little biased.
-
Kakoune Code Editor
Judging by https://github.com/mawww/golf kakoune is capable of completing the majority of the same editing tasks as vim in a very similar amount of keystrokes. The main advantage of multiple selections is that you can see which text you will operate on ahead of time, rather than having to first select which operation you want (delete/yank/change/etc) and then which text it will affect. I think pointing out that vim's selections aren't as capable as kakoune's is a fair response, and saying that you can accomplish similar things without selections is a bit of a deflection.
What are some alternatives?
tabs.kak - Kakoune buffers as tabs in the status line.
nvim-config
kakoune-easymotion - kakoune plugin for navigating like the easymotion vim mode
one.kak - Atom "One" color schemes for Kakoune.
dance - Make your cursors dance with Kakoune-like modal editing in VS Code.
helix - A post-modern modal text editor.
kakoune-wakatime - WakaTime! For Kakoune! Yay!
incsearch.vim - :flashlight: Improved incremental searching for Vim
config - dotfiles
helix - A post-modern modal text editor.