5 ms·

The last one is compelling, but the new "editing language" and paradigm that's been put together is _really_ compelling. Being able to see what a "sentence" is

The last one is compelling, but the new "editing language" and paradigm that's been put together is _really_ compelling. Being able to see what a "sentence" is going to do as you're typing it is a huge improvement on vim. I _love_ vim, but executing complex commands is like shouting into a dark tunnel and hoping the person on the other end understands what you were trying to say.

nerdponx 10y ago
You know there's a setting to display the current command in the status line right?
- kaoD 10y ago
  Unless I misunderstood that won't show the result of the command.
- proaralyst 10y ago
  There's a difference in knowing what you've typed and what that means. Displaying the current chord protects against typos and losing track, but doesn't help you understand what your command is doing. I'm not convinced I'll switch to Kakoune (as I've got a lot of momentum in Vim, not just with the editing language) but the automatic display of the _semantics_ of your current chord is an interesting idea.
DennisP 10y ago
That's why I tend to use visual mode. It sounds like Kakoune is basically visual mode by default, which is cool but not that different. This example was a bit silly: "dtf will delete to next f, if you then realize that was one f before the one you targeted, you need to undo, go back to your initial position, and try again with d2tf." There's no need to undo. Just follow up with a dot and you're done. Which pretty much illustrates my other general strategy, which is to edit incrementally without worrying about getting each command perfect. (Which is not to say I don't find Kakoune intriguing.)
- jxy 10y ago
  Which is to say that they don't understand vim, or rather, they don't even grok vi. You can't beat your enemy if you don't understand your enemy. "Go ahead and down vote more, I just wish you guys can learn more of vi, so you can truly deliver something better. So far, these surface scratching alterations only build on irritations of those vi first-timers. Good luck. "By the way, I use acme when I have graphics interface, nothing beats sam's structured regexp editing capability, apart from writing perl scripts. Learn something, guys.
  - martanne 10y ago
    You can be sure that the Kakoune authors are familiar with vi(m). Having said that, if you like both vi(m) and the structural regular expression support of sam/acme you might be interested in vis which combines the two: https://github.com/martanne/vis https://github.com/martanne/vis
  - omtose 10y ago
    >I just wish you guys can learn more of vi, so you can truly deliver something better. So far, these surface scratching alterations only build on irritations of those vi first-timers Mind expanding on that, or are you just going to whine? It's not like vi is the ultimate tool.
- Roboprog 10y ago
  The dot trick is fine, unless you wanted to paste the deleted text somewhere afterward, in which case you need to pick it up in one go. Otherwise, yeah, dot is great. I love using that for repetitive stuff on "tabular" copied entries that I'm not thinking real hard about transforming. (E.g. - 5 lines or so that I'm not cooking up a regex or an perl/awk spell to transmute)
  - jxy 10y ago
    > The dot trick is fine, unless you wanted to paste the > deleted text somewhere afterward, in which case you > need to pick it up in one go. No. "1p.

nerdponx 10y ago

You know there's a setting to display the current command in the status line right?

kaoD 10y ago
Unless I misunderstood that won't show the result of the command.
proaralyst 10y ago
There's a difference in knowing what you've typed and what that means. Displaying the current chord protects against typos and losing track, but doesn't help you understand what your command is doing. I'm not convinced I'll switch to Kakoune (as I've got a lot of momentum in Vim, not just with the editing language) but the automatic display of the _semantics_ of your current chord is an interesting idea.

DennisP 10y ago

That's why I tend to use visual mode. It sounds like Kakoune is basically visual mode by default, which is cool but not that different. This example was a bit silly: "dtf will delete to next f, if you then realize that was one f before the one you targeted, you need to undo, go back to your initial position, and try again with d2tf." There's no need to undo. Just follow up with a dot and you're done. Which pretty much illustrates my other general strategy, which is to edit incrementally without worrying about getting each command perfect. (Which is not to say I don't find Kakoune intriguing.)

jxy 10y ago
Which is to say that they don't understand vim, or rather, they don't even grok vi. You can't beat your enemy if you don't understand your enemy. "Go ahead and down vote more, I just wish you guys can learn more of vi, so you can truly deliver something better. So far, these surface scratching alterations only build on irritations of those vi first-timers. Good luck. "By the way, I use acme when I have graphics interface, nothing beats sam's structured regexp editing capability, apart from writing perl scripts. Learn something, guys.
- martanne 10y ago
  You can be sure that the Kakoune authors are familiar with vi(m). Having said that, if you like both vi(m) and the structural regular expression support of sam/acme you might be interested in vis which combines the two: https://github.com/martanne/vis https://github.com/martanne/vis
- omtose 10y ago
  >I just wish you guys can learn more of vi, so you can truly deliver something better. So far, these surface scratching alterations only build on irritations of those vi first-timers Mind expanding on that, or are you just going to whine? It's not like vi is the ultimate tool.
Roboprog 10y ago
The dot trick is fine, unless you wanted to paste the deleted text somewhere afterward, in which case you need to pick it up in one go. Otherwise, yeah, dot is great. I love using that for repetitive stuff on "tabular" copied entries that I'm not thinking real hard about transforming. (E.g. - 5 lines or so that I'm not cooking up a regex or an perl/awk spell to transmute)
- jxy 10y ago
  > The dot trick is fine, unless you wanted to paste the > deleted text somewhere afterward, in which case you > need to pick it up in one go. No. "1p.