#kakoune — Public Fediverse posts

I am considering moving away from Neovim.
Any idea if there are any assholes (misogynists, racists, fascists) involved in Kakoune’s development? It doesn’t seem tainted by slop, or did I miss anything?

https://kakoune.org/

#neovim #vim #kakoune #fuckAI

Apergol & tupperVim

https://keskonfai.fr/events/f3dcfdba-b9ee-4dbe-9862-600d561866f5

RE: https://mamot.fr/@PacoVelobs/117354448020853259

Deux jours avant celui de #Lyon, il y a un #tupperVim à #Grenoble aussi. Qu’on se le dise !

#Vim #Neovim #Helix #Kakoune #DoomEmacs

Oyez, oyez ! Jeudi 29/10, y a #Apergol + #tupperVim dans les locaux d’OVH à #Lyon !
– De 19h à 20h, deux tracks parallèles : initiation #Vim pour les néophytes, apéro et #poticlaviers pour les autres.
– De 20h à 22h, atelier Vim (et #Neovim, #Kakoune, #Helix, #DoomEmacs…).

La salle est immense, donc y aura moyen de jouer avec les poticlaviers dans une moitié de salle pendant que les Vimistes œuvreront. @NuclearSquid sera là avec des #Quacken et #QMx2040 en test.

Qu’on se le dise ! 🖖

Is anybody using the VIS editor?

https://sr.ht/~martanne/vis/

I’m really curious about it but I would need some bootstrap tutorial like "VIS for Vim users". I’m still really confused about it.

(yeah, I’m planning to leave Neovim. Will probably ends on Vim-classic once it is packaged in #debian ). Also like #kakoune a lot but Vim-muscle memory is too strong for now.

#vim #vis #neovim

There's a fair chance of a Helix fork (especially given the plugin changes), but if I had to switch editor, #Kakoune was on my radar.

Sadly I have the same #ClaudeAI "A user you’ve blocked has previously contributed to this repository. " banner when I view their repository, but again the search comes up empty: https://github.com/mawww/kakoune/commits?author=claude

Has #GitHub broken something again... at the command line there are 3 commits dated March 2026 with "Co-Authored-By: Claude Opus 4.6 <[email protected]>"

See https://github.com/mawww/kakoune/issues/5463

@marcello_tamburini i think so. i been messing with piping it some random data out of #duckdb structured in #csv and it works! It is a small niche, but a very nice one. Now to think of how to pipe using #kakoune for random snippets. 😅

Ok. #kakoune session handling is out of this world. You can have the same session span multiple terminals! May not sound like a lot, but it unlocks full cross section file editing! ON THE SAME FILE!! 🤯

Yes. It's missing native #treesitter, but like... i can live with that gap for this skill. 😆

I should've seen this coming. After years using #helix, I'm trying out #kakoune. 😅

May seem similar, but there's real differences. But the EVERYTHING can be a command is kind of brilliant.

https://ficd.sh/blog/kakoune-is-a-text-editor/

kakoune's latest release is faster :D i was confused why loading my kakrc config was instant. 😩

#kakoune #kakouneeditor

Uhhh I finally put kak-sql together. It allows querying SQL databases from within Kakoune. It's simple but could be helpful to others: https://sr.ht/~gbrlsnchs/kak-sql

#kakoune #sql #plugin

I started working on a Kakoune plugin that allows running SQL queries from your editor, by selecting them... let's see how far I can get...

#kakoune #sql

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.

#Vim #Neovim #nvim #Helix #Kakoune #FOSS #slopocalypse

@sotolf @thedoctor @paul @mirabilos

I think #kakoune tries to bridge the gap between user-friendly and "power-user-friendly" (to attempt to sum up what you were saying into a single term).

Unfortunately, it broke some muscle memory for me, and was therefore a non-starter.

Not hating on the project, I think it's brilliant. I just personally can't use a vi-like editor that isn't a pretty strict superset of vi keybinds.

Anyone know #kakoune's AI policy?

Good news for Deno and Kakoune users: I have implemented a fix for paths with brackets (i.e. Fresh dynamic pages)

I have also added support for virtual documents when using goto-definition (i.e. deno:// paths).

Merge requests are open, but in case they're not merged yet, here's my fork: https://github.com/gbrlsnchs/kakoune-lsp/tree/deno

#kakoune #deno #lsp

Tiny steps, 15 minutes of tinkering each day or so. I'm finally getting the hang of what a workflow using Kakoune could look like.

Now to actually learn the editing model, and fill the workflow gaps (equivalent to quickfix list, etc).

#kakoune

Getting ergonomic keybindings interacting with, say, tmux panes, requires a good read of the Kakoune documentation on commands, kakrc, mappings etc. Having to learn about this early on can feel like a hurdle, but also now I'm much more ready to bend it to my liking right after.

#kakoune

Settled on always using it inside tmux. Now fzf-tmux can be used to open in a split. That's enough to be usable to me.

Also Kakoune itself integrates with tmux very well out of the box: for instance, :new spawns a Kakoune client attached to the same session in a new tmux window by default.

#kakoune #tmux

Struggling a bit to give Kakoune an honest tryout. I think it's cause of its philosophy. For instance, the (archived) fzf plugin will spawn a "new terminal" (depends on what I'm running in) or, if it's tmux, use its splits. I'm used to more complex windowing capabilities from Neovim or Emacs, but I think that's by design as far as I understand.

Very interesting, but a bit hard to start out with an open mind for someone as settled-in as me 😅

#kakoune

Having configured Neovim to a point where I'm quite happy with it, why do I now feel the urge to do the same with #kakoune? I wonder if it's FOMO or even if I'm just always chasing a thing that's "more special" (in the sense of fewer people using it)...

“How I’m Using Helix Editor”, Artem Golubin (https://rushter.com/blog/helix-editor/).

Via HN: https://news.ycombinator.com/item?id=45559076

#Helix #Editors #Text #TextEditors #Vi #Vim #Kakoune

#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

#Vi #Editors #TextEditors #TUI #Text #UX

Thanks to the dict:// protocol, I was able to implement a lookup word definition plugin to #kakoune in ~20 lines of code

define-command -override lookup_word -docstring "Lookup word under selection" -params 0..1 %{
evaluate-commands %sh{
if [ -n "$1" ]; then
WORD="$1"
else
WORD="$kak_selection"
fi # Fetch the definition and remove noise
definition=$(
curl "dict://dict.org/d:$WORD" 2>/dev/null \
| tr -d '\r' \
| grep -v '^[0-9]' \
| sed '/^\.$/d'
)
printf "info -title Definition %%{%s%%}" "$definition"
}
}

Vous utilisez Vim avec les flèches ? Ou peut-être avec HJKL ? Dans les deux cas, vous sous-utilisez complètement votre éditeur, et ma conf au prochain @capitoledulibre est faite pour vous !

#Vim (comme #Neovim, #Helix, #Kakoune…) dispose d’un ensemble de commandes de déplacements bien plus pertinentes qu’un simple pavé de flèches, fût-il proche de la position de repos.

https://cfp.capitoledulibre.org/cdl-2025/talk/LKKPJB/

#CdL #CdL2025 #Ergonautes

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.

https://github.com/sst/opencode
https://aider.chat/

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!

also here to holler about kakoune! you can get real fancy with kakoune scripting, since it's a designed as a unix tool that does One Thing and integrates well with other tools that also do things. kak's syntax is its underlying syntax--it's not like helix or nvim where the bindings tie to function names, so yeah like sarah said as you're writing out your extra functionality, the definition of d is… d, even if in your config you have bound a different key to action d in normal mode (or d to a different action)! (you can absolutely use a different key for the delete action, you just do it by binding that key to d. example config from someone using the bépo layout)

anyhow I love kakoune and have been using it full-time for a couple years now, definitely give it a look. helix is also an interesting one to look at on the batteries-included side of things, kak-inspired movement paradigm over vim concepts.

I've turned #kakoune into a #lisp machine by connecting it to #guile . It's able to evaluate selections and I just set up the first macro for defining commands.

#emacs #linux #unix #guix #theWorkshop

Hyperlinks!!

#kakoune #linux #unix #ShareYourDesktop

@ZoDoneRightNow It's nice, but I liked #Helix more than #Kakoune. Helix has a much bigger community IMO and they are close to adding Scheme as the extension language, which can be game-changing. I'm on the fence about the "select + action" approach of Kakoune and Helix (compared to classic vim), but it's fairly easy to get used to it.

#textEditor #vim #emacs #kakoune #foss
I’ve been using Emacs with evil mode for a while now but I just stumbled into an editor called Kakoune. Has anyone had any experience with it? How does it compare to other modal text editors? Is it worth trying?