#kakoune — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kakoune, aggregated by home.social.
-
Kasane: New drop-in Kakoune front end with GPU rendering and WASM Plugins
https://github.com/Yus314/kasane
#HackerNews #Kasane #Kakoune #GPU #rendering #WASM #plugins #open #source
-
I wish I could switch to a completely slop-free editor without compromising my workflow too much.
Helix would be a great alternative: Its mappings seem a bit more consistent than Vim’s, also it has Tree-sitter, LSP and fuzzy pickers already built-in. But it lacks some features (digraphs, extensibility, folding – in that order).
I also had a look at Kakoune, which also seems alright, but I don’t like that tabs and splits are delegated to the terminal emulator, a multiplexer or window manager. I respect that decision, but I’d prefer that feature to be built-in.
For now, I’ll stick to Neovim. At least they have a policy that makes LLM users check and sanitise the generated code (https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#ai-assisted-work), although I’d prefer if they’d outright ban it.
-
“How I’m Using Helix Editor”, Artem Golubin (https://rushter.com/blog/helix-editor/).
-
#Kakoune and #Helix are intriguing modal editor alternatives for #Vim:
“Notes On Switching To Helix From Vim”, Julia Evans (https://jvns.ca/blog/2025/10/10/notes-on-switching-to-helix-from-vim/).
On HN: https://news.ycombinator.com/item?id=45539609
On Lobsters: https://lobste.rs/s/rahklm/notes_on_switching_helix_from_vim
-
Just wanna say that #opencode is much better than #aider. Not committing my changes with every prompt. Easily able to open my editor for the entire conversation. Pressing tab to switch between build and plan mode. And it not being written in python makes me feel better (though looks like it is go+bun... not sure if typescript feels much better than python). It really fits into my cli workflow using #kakoune as my main editor.
I know a lot of people have concerns about LLMs in this space, but they are getting very useful.
-
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
-
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
-
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
-
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
-
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
-
Felix on Helix:
“A Review Of Helix After 1.5 Years”, Felix Knorr (https://felix-knorr.net/posts/2025-03-16-helix-review.html).
Via Lobsters: https://lobste.rs/s/miyoai/review_helix_after_1_5_years
#Helix #Kakoune #Vim #Vi #Editor #TextEditor #ModalEditor #Review
-
and finally, this is very much a kakoune thing, but i don't think selection and navigation should be different things. and more so when im working with blocks of syntax. i'm not working with characters, no do i think in characters. i think in expressions or statements or identifiers or literals.
this is very much a personal opinion, but there's so much room for improvement in this field, i don't see how we've been more or less stagnant for so long. i don't want to use a lisp just so i can use paredit. i want paredit in every language i use.
and doubly finally, you're welcome for me hashtagging every single post in this thread/rant entirely differently. if you're following any of them, you get randomly exposed to some subsection of my thread, without any of the previous parts.
-
Pour qui ne connaîtrait pas encore nos ateliers #tupperVim : on y parle de #Vim (no shit, Sherlock ?), de #Neovim (<3), mais aussi de #Kakoune, d’#Helix ou même d’#Emacs (coucou @ThierryStoehr !), et plus généralement de tous les outils cools qui tournent dans un terminal — le tout, dans un cadre convivial.
(Ne pas assister à ce genre d’événement est une faute de goût.)
-
As a daily driver #KDE #Kate (with its variations: KWrite, GhostWriter, …) will most likely continue to be my main #TextEditor of choice. (The #Marksman LSP makes it very close to something like #Zettlr and #ObsidianMD)
In the console though, I’m conflicted. #Vi is ubiquitous, so knowing its basics is basically a survival skill. That said, I **really** like how Helix’ command workflow (borrowed from #Kakoune) is visual selection ↦ action (Vi is action ↦ selection).
-
Very interesting:
“Why Kakoune — The Quest For A Better Code Editor” [2016], Maxime Coste (https://kakoune.org/why-kakoune/why-kakoune.html).
Via HN: https://news.ycombinator.com/item?id=36424256 (originally: https://news.ycombinator.com/item?id=13165919)
On Lobsters: https://lobste.rs/s/gwdwjb/why_kakoune_quest_for_better_code_editor
-
Have you ever tried https://helix-editor.com/ ? It is incredible! #vim #kakoune #modaleditor
-
#kakansi is a #publicdomain ANSI to highlight translator.
kak-ansi renders text that is colourised in ANSI escape sequences using #Kakoune's builtin colour highlighting system. kak-ansi has several commands, all of which remove escapes and replaces them with highlighting.
Website 🔗️: https://github.com/eraserhd/kak-ansi
-
Do you enable line numbers in the margin of your text editor? (boost for more data!)
#emacs #vim #vi #nano #microeditor #kakoune #kak #vis #viseditor #vscode #atom #texteditor #notepadplusplus #notepad #text #editors #programming #coding #writing #poll #linenumbers
-
Finally! #Parinfer for #Guix ! Now I can edit Scheme in #Kakoune UwU.
https://git.sr.ht/~raingloom/guix-packages/commit/e51d9797c30a2b6bdd035677c855338dc706e714 -
I did a thing.
Kakoune (-ish) mode for VSCode. It's just the very basics right now, but I'll keep adding to it while there are things I miss from actual Kakoune.
https://marketplace.visualstudio.com/items?itemName=reykjalin.vscode-kakoune
