3 ms·
Interesting. I had this experience with Kakoune: https://lobste.rs/s/v17gol/switching_sublime_text_from_vim_2017#c_7dbqc1 https://lobste.rs/s/v17gol/switching_s
by akkartik 7y ago
Interesting. I had this experience with Kakoune: https://lobste.rs/s/v17gol/switching_sublime_text_from_vim_2017#c_7dbqc1 https://lobste.rs/s/v17gol/switching_sublime_text_from_vim_2.... I'm curious if you expect to improve on it along the dimensions I mentioned.
- dpc_pw 7y agoHa! I have a very similar experience and I agree with all your points. I really enjoy the basic experience and `kak` is my main text editor ATM, but some details and parts of the philosophy are infuriating me. I started `breeze` as a prototype way to show kakoune author how kak could potentially work https://github.com/mawww/kakoune/issues/2590 https://github.com/mawww/kakoune/issues/2590 , and later decided that actually I could maybe push it further into a full new text editor. I'd like to make it more natural to use, and get rid of the (IMO) pointless idiosyncrasies like the plugin API being keystroke based. I'd like to also make it easy to embed into other software, so that there's some hope that it could be easily integrated into existing software, so I'm not doomed to forever switch between kakoune and classic-vi editing.
- adrusi 7y agoThe lack of built-in window management is a major feature of kakoune for me. I try to delegate all window management to my window manager, including such things as browser tabs, so I like that kakoune is designed to be used like that. The biggest downside of kakoune's approach for me is that it makes vimdiff-functionality pretty hard to achieve.