golf
one.kak
| golf | one.kak | |
|---|---|---|
| 3 | 1 | |
| 118 | 19 | |
| - | - | |
| 9.2 | 6.3 | |
| about 2 months ago | almost 2 years ago | |
| Shell | KakouneScript | |
| The Unlicense | MIT License |
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.
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.
one.kak
-
Kakoune Code Editor
Oh you're fine! I didn't think you were being flippant. I've been using One Darker (One Dark with a darker background) for two years and don't have any plans to change anytime soon. Here's the source for the theme if you're interested. It has gotten a little bit more complex than I described in my post, due to supporting various plugins, but it's still pretty easy to understand.
https://github.com/raiguard/one.kak/blob/main/colors/one-dar...
What are some alternatives?
nvim-config
kakoune-phantom-selection - Work on multiple selections, one at a time
symflower-kakoune - Unit test generation for the Kakoune editor with Symflower
helix - A post-modern modal text editor.
kakoune-easymotion - kakoune plugin for navigating like the easymotion vim mode
neovim - Vim-fork focused on extensibility and usability
kakoune-wakatime - WakaTime! For Kakoune! Yay!
incsearch.vim - :flashlight: Improved incremental searching for Vim
saturn.kak - Dark 256-color colorscheme for Kakoune
helix - A post-modern modal text editor.
kakoune-smooth-scroll - Smooth scrolling for Kakoune with inertial movement