I'm hoping neovim will be able to adapt these ideas in the future.
They're addressing all the hardcoded parts so it should be possible to make any of these with an addon / some nvimrc magic.
Kakoune – An experiment for a better code editor
11–20 of 36 posts
Re: Kakoune – An experiment for a better code editor
#12[deleted]
Re: Kakoune – An experiment for a better code editor
#13I've played with Kakoune a little bit not that long ago. It's actually pretty nice. By far the best feature is the popup that lists all the sub-actions for chords: imagine if, when you press "g" in Vim, it lists all keys you press after AND what they do. It makes it very easy to figure out new behavior. The idea of working on selections is also very intuitive and works well, both in vim compatability and ease of use.…
Auto-promotion here :-D Check Spacemacs, it is an Emacs configuration usable by Vim users out of the box. It has the feature you mentioned powered by the which-key package.
Re: Kakoune – An experiment for a better code editor
#14You'll want to take a look at your site's theme on mobile devices. On my iPhone 6 on iOS 9 (Safari), the navigation bar is fixed at the top half of the pane and takes up over half the screen.
Same here. Here's a picture. https://twitter.com/zlrth/status/660671388693323777
iPhone 5s, iOS 9.1. sorry to all reading my tweet about the snark. But I just find it so sad that I have so much rendering power on desktop (JavaScript on/off, elinks web browser, my rss reader), but if some silly CSS thing borks the mobile page, there's nothing I can do.
Re: Kakoune – An experiment for a better code editor
#15I've played with Kakoune a little bit not that long ago. It's actually pretty nice. By far the best feature is the popup that lists all the sub-actions for chords: imagine if, when you press "g" in Vim, it lists all keys you press after AND what they do. It makes it very easy to figure out new behavior. The idea of working on selections is also very intuitive and works well, both in vim compatability and ease of use.…
Auto-promotion here :-D Check Spacemacs, it is an Emacs configuration usable by Vim users out of the box. It has the feature you mentioned powered by the which-key package.
I'm a spacemacs convert after using vim for 2 years. This editor + configuration is extremely hard to beat. I just pulled from master after using it full time for two months and updates were amazing.
Way better ergonomics than vim and elisp is extremely easy to hack on.
Re: Kakoune – An experiment for a better code editor
#16It looks nice, and I assume the underlying code is less gnarly than vim's, but I don't see the radical improvement over vim which would make me switch (also, obviously, it's not going to benefit from the huge ecosystem of vim plugins).
What I think would be a killer for a vim successor would be to keep the best-in-class editor functionality, add decent extensibility (not vimscript) in the core product. Then add support for stuff commonly found in IDEs: notion of projects/subprojects, API to support plugging syntax parsers easily, source control integration, etc., and offer core plugins for a few popular languages.
Re: Kakoune – An experiment for a better code editor
#17I tried switching to this editor permanently from vim. The selection based movements are asurdly good, I could kill for something like this in vim. However I couldn't stick with it for two reasons. The first is when I went to figure out how to customise it, I found that the customisation is essentially vim like but weaker. Everything is hardcoded like it would be in vim but with less options. If you're used to Emacs…
I'm guessing it wouldn't be too difficult to clone the motion system et. al. in emacs?
Re: Kakoune – An experiment for a better code editor
#18I've played with Kakoune a little bit not that long ago. It's actually pretty nice. By far the best feature is the popup that lists all the sub-actions for chords: imagine if, when you press "g" in Vim, it lists all keys you press after AND what they do. It makes it very easy to figure out new behavior. The idea of working on selections is also very intuitive and works well, both in vim compatability and ease of use.…
well intentioned nit-pick: vim commands starting with a g are NOT chords, and that's very important from am usability standpoint. For the most part vim avoids chords, while E-macs embraces them. It's a question of whether you want to strain your hands (chords/emacs) or your brain (modal/vim) for triggering infrequent commands.
Re: Kakoune – An experiment for a better code editor
#19I've played with Kakoune a little bit not that long ago. It's actually pretty nice. By far the best feature is the popup that lists all the sub-actions for chords: imagine if, when you press "g" in Vim, it lists all keys you press after AND what they do. It makes it very easy to figure out new behavior. The idea of working on selections is also very intuitive and works well, both in vim compatability and ease of use.…
well intentioned nit-pick: vim commands starting with a g are NOT chords, and that's very important from am usability standpoint. For the most part vim avoids chords, while E-macs embraces them. It's a question of whether you want to strain your hands (chords/emacs) or your brain (modal/vim) for triggering infrequent commands.
I like to think of Vim's way of doing things as arpeggios, where Emacs uses chords.
Re: Kakoune – An experiment for a better code editor
#20Earlier quoted context omitted.
Auto-promotion here :-D Check Spacemacs, it is an Emacs configuration usable by Vim users out of the box. It has the feature you mentioned powered by the which-key package.
I'm a spacemacs convert after using vim for 2 years. This editor + configuration is extremely hard to beat. I just pulled from master after using it full time for two months and updates were amazing. Way better ergonomics than vim and elisp is extremely easy to hack on.
As a counterpoint - I went back to VIM after a month of spacemacs. I've actually put in the effort to learn the keybindings for all the relevant tasks I needed and the way Emacs works internally, as much as it's possible in a month.
I was doing Clojure and the main problem for me was the less fluent editing - most commands in vim are at least one keystroke shorter. The other big problem are non-evilified plugins that completely mess up the workflow - you constantly keep switching between "I'm in VIM" and "I'm in Emacs" mindset. Also, emacs feels a bit more sluggish, although that may be just CIDER.
The things I loved:
* helm mode - autocompletions for the commands
* consistency - SPC + ... everywhere
* REPL in a buffer