Does anyone use this daily? this gets posted a few times a year to HN but tbh it looks like someone just re-invented vi. Which seems kindof like creating a new religion. It can be done, but even the best televangelist isn't going to hold a candle to the spread of the catholic church.
I use it daily for many years, being a user of vim for 20 years or so. I could not come back to vim now, I find the kakoune way more efficient. I find two annoying things : - U need to make a lot of tuning to make it usable because there is now tab management, no clipboard, etc.. - U need always the last version of C++ compiler to make it compile. This is annoying on professional VMs that are way behind the current v…
Kakoune Code Editor
131–140 of 176 posts
Re: Kakoune Code Editor
#132Earlier quoted context omitted.
I am using it daily, as my sole editor, for a little more than a year now. Before that I used Neovim. Most important reasons for the switch are: * Leaves window management to the window manager, so it works much better with a tiling wm. I wish all applications did this. * Selecting first and then specifying an action works way better than the other way around, as it is done in the Vim family. Edit: regarding the comm…
> * Selecting first and then specifying an action works way better than the other way around, as it is done in the Vim family. There is visual mode in vim too you know. That's for doing exactly what you describe. I use that when I'm unsure about the movement I need for an action.
Re: Kakoune Code Editor
#133> The first thing to realize is that non-modal text editors are extremely biased towards insertion.
I made https://enso.sonnet.io and I 100% agree with Maxime on this one
Re: Kakoune Code Editor
#134Earlier quoted context omitted.
I tried to use it enough to see if I could switch to it from (neo)vim. I liked a lot of the ideas in it, and in some ways I liked it more than vim, but it was missing some functionality that I just couldn't live without. Some things could be solved by plugins that just didn't exist yet, but others, I couldn't even see a way a plugin could be implemented. In particular, there isn't any way to get a diff mode comparabl…
I don't understand the new line thing at the end. I haven't used a utility or app in -decades- that cared about whether you have a blank final line.
Re: Kakoune Code Editor
#135Earlier quoted context omitted.
That's also what I thought as a Vim user before I had access to Kakoune's multiline editing. It changed my mind and might change yours too if you give it a chance
I used editors with multiline editing capabilities in the past. There are only 2 usecases where it was of any value to me: If I have to write multiple lines in a similar fashion, or if I have to edit the same thing in a similar fashion in several places at once. Both can be done much easier by using a regular expression.
Re: Kakoune Code Editor
#136Does anyone use this daily? this gets posted a few times a year to HN but tbh it looks like someone just re-invented vi. Which seems kindof like creating a new religion. It can be done, but even the best televangelist isn't going to hold a candle to the spread of the catholic church.
Re: Kakoune Code Editor
#137Does anyone use this daily? this gets posted a few times a year to HN but tbh it looks like someone just re-invented vi. Which seems kindof like creating a new religion. It can be done, but even the best televangelist isn't going to hold a candle to the spread of the catholic church.
Multiple selections with the visual preview before action was the key feature for me-- it is a nice affordance compared to having to mentally model what an operation would do with a vim movement.
Re: Kakoune Code Editor
#138Earlier quoted context omitted.
go read emacs-devel to find out where the focus is. If by focus you mean distilled yak shaving, then emacs-devel is the place to be. Emacs is going nowhere because elisp makes it too easy to work on the plugins relative to the C core which was showing its age 15 years ago.
The C core is getting a feature to compile elisp to native code in the forthcoming Emacs 28. I've yet to try it, but I understand it offers a significant speed boost. It's certainly true that the core C codebase has some major parts that are aging poorly, but it's not true to say it's going nowhere. (As one who has shaved plenty of yaks and occasionally reads emacs-devel, I'd say it's the place for distilled bikeshed…
I'm using the "native comp" (of elisp to native code) since it's available (years already now? Don't remember exactly but a long time). That, combined with a fast JSON parsing lib and LSP and Emacs is definitely not just the Emacs of 15 years ago.
Other things happened to the Emacs world too: ivy/avy/counsel (and maybe lispy and hydra) are stuff I couldn't live without anymore.
Re: Kakoune Code Editor
#139Does anyone use this daily? this gets posted a few times a year to HN but tbh it looks like someone just re-invented vi. Which seems kindof like creating a new religion. It can be done, but even the best televangelist isn't going to hold a candle to the spread of the catholic church.
Kakoune is a fantastic tool of rare quality. I find it a joy to use.
Re: Kakoune Code Editor
#140Does anyone use this daily? this gets posted a few times a year to HN but tbh it looks like someone just re-invented vi. Which seems kindof like creating a new religion. It can be done, but even the best televangelist isn't going to hold a candle to the spread of the catholic church.