Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kakoune Code Editor

kakoune.org

Post reply on HN
Print view View original

101–110 of 176 posts

Re: Kakoune Code Editor

#101

Post by cduret »

mushufasa wrote: post #2

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 use it daily for many years, being a user of vim for 20 years or so. I could not come back to vim now, I find the kakoune way more efficient.

I find two annoying things :

- U need to make a lot of tuning to make it usable because there is now tab management, no clipboard, etc..

- U need always the last version of C++ compiler to make it compile. This is annoying on professional VMs that are way behind the current version of gcc.

I would suggest the community to make better documentation for plugin development which can be very hard to learn

Re: Kakoune Code Editor

#103

Post by 414owen »

skavi wrote: post #12

Check out helix [0] for a kakoune inspired editor with some nice modern features included by default. [0]: https://helix-editor.com/

Helix is my daily driver and it's got such nice defaults I haven't even bothered configuring it.

For modern code editing it's just faster. Everything's built in natively.

Re: Kakoune Code Editor

#104

Post by kybernetikos »

usrbinbash wrote: post #87
jzm2k wrote: post #41

Earlier quoted context omitted.

I think multicursor is more flexible. I can visually select N lines and use regex to place the cursors and then modify the text in multiple places simultaneously. Kakoune also provides a multicursor similar to the visual block mode that Vim offers but I find myself using that only in very specific situations like "these 5 lines should all start with this keyword" or whatever.

imo, Multiline cursors are one of these features that look and feel cool, but are rarely, if ever, really useful.

That's shocking to me. Ctrl-D in visual studio code and alt-J in jetbrains are some of my most used key combinations. Even alt-click in visual studio code is sometimes extremely useful. It's like the ability to record and play back a macro multiple times, except you do it interactively and can see / fix / add things as you go.

Re: Kakoune Code Editor

#105

Post by mbarbar »

konart wrote: post #67
mbarbar wrote: 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

Exactly what @ziml77 said.

Even in the case of simple "wd", sometimes I have multiple cursors I am operating on at the same time (e.g. from complex regex or just through selecting multiple lines at once) so each cursor could point to fairly different things. Then, the visual feedback becomes very useful.

Re: Kakoune Code Editor

#106

Post by shric »

stjohnswarts wrote: post #55
thayne wrote: 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.

There's a few reasons I can think of (some superficial, some significant):

- Github and git will highlight a missing newline in a diff by default.

- POSIX defines a line as having a newline at the end, so if you don't have a terminating new line you may have one fewer lines than you think you have [1]

- If you ever want to append to a text file/source file programmatically with something like echo "something at the end" >> yourfile.txt then you'll be grateful you had the habit of ending everything with a newline.

- If you use a shell that doesn't automatically add one when you do cat filename you'll end up with your prompt sitting awkwardly at the end of the file.

vim, iirc, defaults to automatically adding a newline to any file without you explicitly asking for it, unless you do set noeol and set binary or, in versions newer than 7.4, set nofixendofline

[1] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1...

Re: Kakoune Code Editor

#108

Post by yitchelle »

raiguard wrote: post #22
mushufasa wrote: post #2

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've been using Kakoune as my daily driver for almost a year. The thing that made me fall in love was the simplicity, both in daily usage and in extensibility. The biggest "oh wow" moment for me was how easy it was to create a color scheme. In Vim, creating your own color scheme is potentially a huge ordeal, with many edge cases. For example, vim-one's color scheme file is over 800 lines long. By contrast, I created…

I would have thought that creating/adapting a colour scheme is a onetime activity when you start using the editor for your language. Do you update the colour scheme regularly?

Re: Kakoune Code Editor

#109

Post by berkes »

oblio wrote: post #96
sidkshatriya wrote: post #39

Earlier quoted context omitted.

Shelling out was a turnoff for me also initially but I've learn to embrace it. Kakoune tries not to re-invent the wheel. If sh/sed/awk/perl/other unix tools do the job well, might as well use them. That is the philosophy I think. I like the fact that using Kakoune has improved my shell script skills like crazy. (Posix) shell scripting is just everywhere and is an important skill to have. Kakoune uses shell integratio…

> (Posix) shell scripting is just everywhere and is an important skill to have. Not on Windows. Which may or not may matter.

Didn't Microsoft team up with Ubuntu to offer this to Windows users?

I'm out of the loop and haven't touched windows seriously in years (other than to fix WiFi or printer issues for family. Sigh), so I probably misunderstood this Ubuntu in Windows completely.

Re: Kakoune Code Editor

#110

Post by HKH2 »

sidkshatriya wrote: post #63
skavi wrote: post #12

Check out helix [0] for a kakoune inspired editor with some nice modern features included by default. [0]: https://helix-editor.com/

I use Kakoune very extensively. I've tried out Helix a bit though. While I'm adequately informed to make an assessment about Kakoune, my opinion about Helix is more impressionistic. My overall assessment is that Helix has the potential to run away with the Kakoune interested crowd! For a new editor Helix looks shockingly polished! Here is what I like: - Tree sitter is integrated into Helix. Kakoune use a lot of regex…

How did you get Kakoune to segfault?
Post reply on HN