Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kakoune Code Editor

kakoune.org

Post reply on HN
Print view View original

81–90 of 176 posts

Re: Kakoune Code Editor

#81

Post by skavi »

sidkshatriya wrote: post #63
skavi wrote: 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…

> Helix is built in Rust. Kakoune is built in C++. I've encountered the occasional segfault in Kakoune and I would guess that these would be rarer in Helix simply because Rust makes it easy to write "safer" code by default

No segfaults, but Helix is definitely somewhat buggy at the moment, especially on Windows. Panics make it relatively easy to debug though.

Re: Kakoune Code Editor

#82

Post by skavi »

mikojan wrote: post #48
skavi wrote: post #12

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

Have been using this instead of vim for a month now. It's incredible. No messing with plugins and archaic config files. All works out of the box, including LSP integration. Highly customizable still. Extremely fast, too. I love "space-k" (Show docs for item under cursor). The one thing I'm still struggling with is the kakoune-like movements. Maybe I'm doing something wrong, but they do feel inferior to vim's.

what kind of motions are you missing? I prefer helix to default vim, but miss the power of the amazing lightspeed.nvim plugin.

Re: Kakoune Code Editor

#83

Post by skavi »

adam_ung wrote: post #80
mikojan wrote: post #48

Earlier quoted context omitted.

Have been using this instead of vim for a month now. It's incredible. No messing with plugins and archaic config files. All works out of the box, including LSP integration. Highly customizable still. Extremely fast, too. I love "space-k" (Show docs for item under cursor). The one thing I'm still struggling with is the kakoune-like movements. Maybe I'm doing something wrong, but they do feel inferior to vim's.

In Vim you can also hit Shift-k to open docs (I usually use it for manual pages).

In this case, space k will open a popup with docs/definitions provided by the language server.

Re: Kakoune Code Editor

#84

Post by lf-non »

OtomotO wrote: post #62
skavi wrote: post #12

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

Very intrigued, waiting for the wasm-plugins though. There are a few plugins I cannot work without. It's nice they have tree-sitter and lsp out of the box, but I can't live with things like hop[0] [0] https://github.com/phaazon/hop.nvim

It's a bit surprising how many easymotion style plugins (n)vim ecosystem has. I discover a new one every other week or so.

Re: Kakoune Code Editor

#85

Post by reegnz »

DJHenk wrote: post #77
mushufasa wrote: post #2

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

#86

Post by usrbinbash »

DJHenk wrote: post #77
mushufasa wrote: post #2

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

Vim allows me the exact same thing using visual mode. even better, I can still use the powerful move commands in visual mode to control what is selected, before triggering an action on the selection.

Re: Kakoune Code Editor

#87

Post by usrbinbash »

jzm2k wrote: post #41
pletnes wrote: post #25

Earlier quoted context omitted.

What’s the big deal with multiline cursor over visual block mode?

I think multicursor is more flexible. I can visually select N lines and use regex to place the cursors and then modify the text in multiple places simultaneously. Kakoune also provides a multicursor similar to the visual block mode that Vim offers but I find myself using that only in very specific situations like "these 5 lines should all start with this keyword" or whatever.

imo, Multiline cursors are one of these features that look and feel cool, but are rarely, if ever, really useful.

Re: Kakoune Code Editor

#88

Post by usrbinbash »

grayrest wrote: post #29
konart wrote: post #24

Earlier quoted context omitted.

I find it extremely subjective. "delete word" is much better than "word delete" imo. Also `dw` sounds more logical if you think about user input speed\pauses. If I press `w` I want to move to the next word immediately. In case were `wd` deletes a word - there should be some lag, no?

Doing the motion first lets you visually confirm the range before invoking the command. You also have the opportunity to adjust the range if you didn't get it quite right. Mnemonically the vim order works better for English but in practice I find the visual feedback from selection better for anything even moderately complex. An example would b `f` or `t` since I tend to hit the letter I was aiming for earlier than I…

The same visual feedback exists in vim.

    vwww
selects the next 3 words visually. I can now press `d` to delete them.

Re: Kakoune Code Editor

#89

Post by OskarS »

grayrest wrote: post #29
konart wrote: post #24

Earlier quoted context omitted.

I find it extremely subjective. "delete word" is much better than "word delete" imo. Also `dw` sounds more logical if you think about user input speed\pauses. If I press `w` I want to move to the next word immediately. In case were `wd` deletes a word - there should be some lag, no?

Doing the motion first lets you visually confirm the range before invoking the command. You also have the opportunity to adjust the range if you didn't get it quite right. Mnemonically the vim order works better for English but in practice I find the visual feedback from selection better for anything even moderately complex. An example would b `f` or `t` since I tend to hit the letter I was aiming for earlier than I…

> Doing the motion first lets you visually confirm the range before invoking the command. You also have the opportunity to adjust the range if you didn't get it quite right.

It should be noted here that Vim more or less works like this in visual mode. If you go "v " instead of " ", you can visually confirm the range. I can see the argument that it should be the default, though I like the fact that alone in normal mode just moves you around without preparing for a command.

Re: Kakoune Code Editor

#90

Post by dima55 »

raverbashing wrote: post #78
dima55 wrote: post #60

Earlier quoted context omitted.

> Why would you even bother making Emacs look like Kakoune? Because somebody wanted the Kakoune core editor behavior combined with the world of features emacs gives you. > Funny how it seems a lot of Emacs developer time is spent a) making it look like / act like something else Somebody found this useful. Would you have preferred that this person didn't do any of this at all? > and b) making it do things unrelated to…

> Somebody found this useful. Would you have preferred that this person didn't do any of this at all? The usual conversation starters about emacs go "oh you have Spacemacs, you have EVil, you have plugin X, Y, Z, etc, etc" Whereas with other editors the focus is on improving the core experience Plugins are great, sure, but there seems to be an excessive focus on it and most plugins just don't give you the same experi…

You're clearly not involved in the development of emacs, and your perception of the "focus" is based on talking to newbies. Respectfully, go read emacs-devel to find out where the focus is.
Post reply on HN