what's the font that is used on the screenshots ?
I would love to try it in Pycharm IDE/Jetbrain products.
Why Kakoune – The quest for a better code editor
41–50 of 329 posts
Re: Why Kakoune – The quest for a better code editor
#42Looks like an excellent model. I'll probably stick with vim, at least for the time being, but I'm always glad to see new work being done on modal text editors. I agree that vim's model has certain shortcomings, and it's nice to see see someone trying to address them.
The multiple selections thing looks really cool.
Re: Why Kakoune – The quest for a better code editor
#43From the github docs: > " Due to Kakoune relying heavily on being in a Unix-like environment, no native Windows version is planned." Deal breaker right there. If I am going to go to the effort of learning a new editor, it better run on all reasonable platforms - like Vim does.
To be fair, vim is somewhere around a 4th class citizen on Windows. It works, but it ain't pretty.
Plus, with the unix subsystem (minus bugs) you can still run this in Windows. That still amazes me.
Re: Why Kakoune – The quest for a better code editor
#44From the github docs: > " Due to Kakoune relying heavily on being in a Unix-like environment, no native Windows version is planned." Deal breaker right there. If I am going to go to the effort of learning a new editor, it better run on all reasonable platforms - like Vim does.
For what it's worth, it works properly on cygwin (and certainly the linux subsystem too). I know that the author uses it on cygwin too so there is at least some guarantee.
Re: Why Kakoune – The quest for a better code editor
#45Modal text editors are definitely not my thing, but anyway this looks like a huge improvement on vim. Still a shame that it is entirely console-based. It's 2016 people! We've had GUIs for literally decades.
What would a GUI bring to this that isn't possible in the console? You can use a mouse to issue commands to console programs, after all: if you want to use your mouse to scroll through or select regions of text, you can.
Re: Why Kakoune – The quest for a better code editor
#46A better vim sounds great.
That said I suspect most people would be better off learning a good IDE properly, including but not limited to:
* effective navigation and selection using modifier keys and search
* built in refactoring
* project wide as well as single file search/replace, -and this includes regex search AND replace.
This should be quite doable in less than a week compared to a few months to get equally effective in vim.
Edit: let me add that parts of this looks like a huge improvement over vim.
Re: Why Kakoune – The quest for a better code editor
#47It would be interesting to see it as an editing mode in atom.io or vs code!
Re: Why Kakoune – The quest for a better code editor
#48Earlier quoted context omitted.
You can find the editor source, and installation instructions on github: https://github.com/mawww/kakoune
Thanks! However, my point was that people shouldn't have to read comments on HN to be able to find the editor (I thank you for helping me though!) that someone wrote a whole blogpost about.
I agree with you, though it's a frequent issue that blog posts don't link back to the main site. With that said, it's fairly obvious to go to the root domain for something like a blog post, and that's how i found it.
Definitely should include a link, though.
Re: Why Kakoune – The quest for a better code editor
#49A better vim sounds great. That said I suspect most people would be better off learning a good IDE properly, including but not limited to: * effective navigation and selection using modifier keys and search * built in refactoring * project wide as well as single file search/replace, -and this includes regex search AND replace. This should be quite doable in less than a week compared to a few months to get equally eff…
But if you are like me and work in many different languages, you'll have to spend 10 weeks to learn 10 different IDEs, rather than 8 months to learn one Vim.
Re: Why Kakoune – The quest for a better code editor
#50Modal text editors are definitely not my thing, but anyway this looks like a huge improvement on vim. Still a shame that it is entirely console-based. It's 2016 people! We've had GUIs for literally decades.
What would a GUI bring to this that isn't possible in the console? You can use a mouse to issue commands to console programs, after all: if you want to use your mouse to scroll through or select regions of text, you can.
> What would a GUI bring to this that isn't possible in the console?
Not being destructive of user input, for starters.