Live data from Hacker News

Kakoune Code Editor

kakoune.org

151–160 of 176 posts

Re: Kakoune Code Editor

#151

Earlier quoted context omitted.

I've been using Kakoune as my daily driver for almost a year. The thing that made me fall in love was the simplicity, both in daily usage and in extensibility. The biggest "oh wow" moment for me was how easy it was to create a color scheme. In Vim, creating your own color scheme is potentially a huge ordeal, with many edge cases. For example, vim-one's color scheme file is over 800 lines long. By contrast, I created…

I would have thought that creating/adapting a colour scheme is a onetime activity when you start using the editor for your language. Do you update the colour scheme regularly?

I used color schemes as an example, perhaps it was a bad one. I don't update it regularly, no.

As others have said, the appeal of Kak is orthogonality and accessibility. The keybindings are sensibly organized, there is exhaustive autocomplete and on screen documentation, and the configuration language is simple. It is ridiculously easy to write plugins for, because you can use shell scripting, or create a program in any language you want and invoke it from a shell block. Kakoune's LSP plugin is written in Rust and communicates with Kak via the shell.

Re: Kakoune Code Editor

#152
post #145

Earlier quoted context omitted.

You don't need multi-cursor selection in vim. Vim has all the tools necessary to achieve the same end result with the same convenience. [0] Just thinking about what crazy things I've done with macros that multi-cursor would be incapable of handling makes me chuckle. vim doesn't need the fancy features of other editors (except for maybe LSP and tree-sitter for a more IDE-like experience). The core problem is that you…

> vim doesn't need the fancy features of other editors (except for maybe LSP and tree-sitter for a more IDE-like experience). Both of which neovim has. Agree with your premise, though: (n)vim does not need multi-cursor selection, for the reasons have given.

Don't get me wrong, I'm a nvim + LSP + treesitter user. :)

Re: Kakoune Code Editor

#153

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 agree with this one, it's just like creating a new branch kind of lifestyle or something like that.

Re: Kakoune Code Editor

#154
post #26

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 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…

[deleted]

Re: Kakoune Code Editor

#155
post #12

Check out helix [0] for a kakoune inspired editor with some nice modern features included by default. [0]: https://helix-editor.com/

I use Kakoune very extensively. I've tried out Helix a bit though. While I'm adequately informed to make an assessment about Kakoune, my opinion about Helix is more impressionistic. My overall assessment is that Helix has the potential to run away with the Kakoune interested crowd! For a new editor Helix looks shockingly polished! Here is what I like: - Tree sitter is integrated into Helix. Kakoune use a lot of regex…

Kakoune is gimped by the fact that Mawww had children and cannot dedicate nearly as much time to the project as they had planned to. The idea was to have monthly releases, but that quickly fell by the wayside.

Helix is interesting, and built in LSP and Treesitter is really cool, but it feels like it's missing some of the core principles of orthogonality that Kakoune has. It has the potential to overtake Kakoune very quickly simply due to how active its community is.

Re: Kakoune Code Editor

#156
post #12

Check out helix [0] for a kakoune inspired editor with some nice modern features included by default. [0]: https://helix-editor.com/

I gave it a try but I couldn’t figure out how to disable the editor help popups or hide the line numbers. For all the sane defaults, I’d miss the configurability of Vim.

The code is well organized, and compile times are short, so at least it’s hackable.

Re: Kakoune Code Editor

#157

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 tried it for a short time, but given the ubiquitousness of vi/vim, I just couldn't get myself to commit. I want to keep my muscle memory intact for when I have to ssh into a remote computer somewhere. Which, I guess what I'm saying is, it looks like I'll be attending mass this Sunday.

Re: Kakoune Code Editor

#158

There is also Helix, inspired by both Vim and Kakoune, with built-in LSP support. I'm having a great time with it. https://github.com/helix-editor/helix

I just went through the tutorial. It's not bad, though there doesn't appear to be much documentation (there's not even a built-in :help command, and :tutor is rather minimal).

What do you like about it compared to Kakoune?

Re: Kakoune Code Editor

#159
post #145

Earlier quoted context omitted.

Visual mode only allows for a single selection, though

You don't need multi-cursor selection in vim. Vim has all the tools necessary to achieve the same end result with the same convenience. [0] Just thinking about what crazy things I've done with macros that multi-cursor would be incapable of handling makes me chuckle. vim doesn't need the fancy features of other editors (except for maybe LSP and tree-sitter for a more IDE-like experience). The core problem is that you…

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.

Re: Kakoune Code Editor

#160

There is also Helix, inspired by both Vim and Kakoune, with built-in LSP support. I'm having a great time with it. https://github.com/helix-editor/helix

I just went through the tutorial. It's not bad, though there doesn't appear to be much documentation (there's not even a built-in :help command, and :tutor is rather minimal). What do you like about it compared to Kakoune?

0.6
Post reply on HN