Currently trying it. Thanks for the link: The first minutes are really nice. I’m gonna test it for at least one week.
This short starter guide is nice: https://github.com/mawww/kakoune/blob/master/contrib/TRAMPOLINE
Edit a few minutes later: “kakoune adopted”.
I’ve been a happy kakoune user now for, what is it, maybe two years? I honestly don’t think it’s enough of a sea change from vim to switch if you aren’t already interested, or if you aren’t already irritated by some of vim’s rough edges. But it’s a better, more consistent, simpler experience for me.
There is also vis, comparison of vis and kakoune here.
One major difference is that kakoune is being actively developed and has an active community around it, while vis seems to have gone a bit quiet.
I tried vis in the past and ran into quite some rough edges; it didn’t seem to be in a state where it’s “done”.
What kind of “rough edges”?
I particularly remember having to force quit it after it became unresponsive, e.g. related to search prompt editing and resizing the terminal.
I’ve looked into vis yesterday (as well as kakoune) as I’m looking for an editor that supports auto-complete and can jump to definitions like ctags in vi(1). My main reason is to make exploring new and possibly big code bases easier.
It wasn’t clear to me if these features are already supported by vis (I saw mentions of ctags in the issues on github, but nothing concrete). I’ve also seen vis-complete, but it wasn’t quite clear to me how to set this up to span all source code in a repository. Are these things you have working in your vis setup?
There is apparently a plugin for ctags in vis, though I’ve never used them, nor have I used autocomplete, sorry.
kak-lsp will give you both features (and more, including floating docs, param documentation, etc)
Kakoune looks extremely cool, but I’m always stopped by two things:
Oh, super curious, why are you considering a move to Windows? I personally use both OSes from time to time, but never heard of a person publicly speaking about going in this particular direction, so you piqued my interest what are the reasons :)
Windows has AutoHotKey. That’s the only reason.
There is no integrated solution like AutoHotKey for Linux but you can automate almost anything with shell scripts
I had an AHK script that would toggle YouTube between 1x and 1.25x tempo and another that automatically unfaved the playing song on Spotify. AHK is really, really good.
I currently am on Linux and OS-X … and AHK is without a doubt what I miss most about Windows (being able to casually play any game I want is a close second). Not only was everything doable, but it was also all relatively easy. On the Linux side, you can use xdotool and a handful of other tools, and on OS-X you can do hammerspoon and similar, but none of it feels nearly as good IMHO.
“Virtual desktops” – did with AHK. Fixing every annoyance I came across as quickly as I could, AHK. Even automating crazy multi-app flows easily, AHK. The app you have using stupid shortcuts you think should be changed but it doesn’t let you, AHK.
I used to use Xdotool a long time back. Is AutoHotKey very different/better than this?
Yep, it really is IMHO, I miss AHK most days.