Live data from Hacker News

Kakoune Code Editor

kakoune.org

71–80 of 176 posts

Re: Kakoune Code Editor

#71
//Supports all operating systems except windows?! Oh the humanity! When will the discrimination end?//

I love a good editor. I just discovered Joe and am super happy with that. Cross platform key-bindings is very important considering I am using many different operating systems.

Re: Kakoune Code Editor

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

[deleted]

Re: Kakoune Code Editor

#74
post #47

Earlier quoted context omitted.

AFAIK the creator got the inspiration from Vim, but I think the other statements about github, not mentioning vim, etc. Are just products of your imagination

That the landing page doesn't mention vi/vim or open source is definitely a fact. Of course the reason for not mentioning vim was a product of my imagination, but actually I just wanted to say that I think it's odd for them to avoid stating the almost-obvious...

Both the "Learn more about the Kakoune philosophy" and git repo prominently state it's inspired by vim. Why are you thinking they're hiding it just because it's not on the landing page?

Re: Kakoune Code Editor

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

>There's no animation or forced latency. For a short motion that's predictable like `w`, you're typing the d before you actually check the result and it's just as fast as vim but in the opposite order.

Yeah, I just realised we are talking about normal mode basically...

Re: Kakoune Code Editor

#76
post #26

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

I just ran into an issue with that recently. The Pandas library for Python doesn't consume the last line of a CSV unless it's followed by a new line. I would say I couldn't believe that it actually made inject that newline if it wasn't in the input, but Pandas has enough other oddities that it was pretty easy to believe.

Re: Kakoune Code Editor

#77

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 comments and Vim's visual mode, you are right. I like to change my second bullet to "Does not have too many modes, like the Vim family."

Re: Kakoune Code Editor

#78
post #60

Earlier quoted context omitted.

Why would you even bother making Emacs look like Kakoune? Funny how it seems a lot of Emacs developer time is spent a) making it look like / act like something else and b) making it do things unrelated to editing text. There is no focus. It's good that it can do a lot but it doesn't do any of those things well (unless you want to learn some cryptic key combinations that make less sense than vim). Meanwhile the rest o…

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

Re: Kakoune Code Editor

#79
post #67
post #66

Earlier quoted context omitted.

In my mind I read "wd" as "select word, delete selection" which matches well with the visual feedback Kakoune gives you.

> which matches well with the visual feedback Kakoune gives you. Do you really need this feedback though? I can understand this when yanking, but if I'm going to delete the word... The whole action take much less that a second and then I proceed with my task. Well, to each their own I guess

You're taking the example too literally. The point is that using the motion first gives opens the possibility of visually confirming what the action will be taken on. The usefulness of that improves when the motion is complex. But nothing forces you to confirm, so if you're confident it's right you can immediately follow the motion with the action. That loses you no time compared to Vim.

Re: Kakoune Code Editor

#80
post #48
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.

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