Kakoune – An experiment for a better code editor
1–10 of 36 posts
Re: Kakoune – An experiment for a better code editor
#2You'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.
Re: Kakoune – An experiment for a better code editor
#3You'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.
It looks like the site's built with GitHub Pages so you could raise an issue for it: https://github.com/mawww/kakoune/issues
Re: Kakoune – An experiment for a better code editor
#4I can't even say how happy it made me that Clippy made it into a CLI program. Is that a common joke I've just missed elsewhere?
Re: Kakoune – An experiment for a better code editor
#5I can't even say how happy it made me that Clippy made it into a CLI program. Is that a common joke I've just missed elsewhere?
Sort of. http://vigor.sourceforge.net/
Re: Kakoune – An experiment for a better code editor
#6You'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.
It looks like the site's built with GitHub Pages so you could raise an issue for it: https://github.com/mawww/kakoune/issues
Why downvote this? The submitter here isn't necessarily the author, so the author is more likely to see this if someone submits an issue for it.
Re: Kakoune – An experiment for a better code editor
#7I'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.
The biggest issue I had with it, that made me return to Vim instead of try and keep with Kakoune, are the lack of options. A lot of the settings appear to be hardcoded, with no way to set them even with : commands. While it does have scripting support, and a lot of the core application is implemented with it, there doesn't seem to be any docs on how it works or any community behind it.
Re: Kakoune – An experiment for a better code editor
#8I 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 insane customization, this is the other end of the spectrum. The stuff that IS customisable works by executing embedded bash scripts[1]!? You can only embed these in specific hooks and places, so it's really limited, and platform specific. Install this on a system missing a bash feature someone is using and who knows how it'll behave.
Basically, the features implemented are gorgeous, but past that I can't stick with it. Just going to consider trying to port the selection based movements to a vim plugin but I think it'll be a challenge.
1: https://github.com/mawww/kakoune/blob/master/rc/clang.kak
Re: Kakoune – An experiment for a better code editor
#9Earlier quoted context omitted.
It looks like the site's built with GitHub Pages so you could raise an issue for it: https://github.com/mawww/kakoune/issues
Why downvote this? The submitter here isn't necessarily the author, so the author is more likely to see this if someone submits an issue for it.
A lot of downvotes happen by accident, as on mobile it's easy to fat-finger the down arrow. No need to comment, typically people will notice the mistake and correct it with upvotes.
If the mods read this, I'd like to put in a suggestion to, on mobile, add CSS that places the down arrow on the right side of the screen, nowhere near the up arrow on the left, and make the icons bigger so you can tap them without having to zoom in. Or if that looks cluttered, make the icons as big as they normally are, but make the clickable space larger using padding rules. This is the biggest UX problem HN has, in my opinion.
Re: Kakoune – An experiment for a better code editor
#10Documentation in PDF available?