@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?
I just tried to learn more of #kakoune .
Is there any way to paste commands all at once instead of typing them in?
Like, paste '%/#define<return>d:wq' and have it execute.
@ericsfraga I'm happy meow user, after I've tried #kakoune editor for some time. Also came from vim originally, fighting with vimscript was not my path.
If you'd prefer to use Kakoune-like keybindings in Neovim, you could try this plugin: https://github.com/mirlge/kak.nvim
it seems kakoune with blinking cursor faces works better on wezterm. i guess i am moving to wezterm then.
@uncomfyhalomacro as much as i love the beauty of #kakoune, i see it as just a demo for the editing language (or paradigm) done right (meaning: not derived from line editors (ed).
as such, it would be a replacement for pico/nano/micro, but (sadly) not for #vim.
@mrmattburgess the discussion on "do one thing and do it well" in relation to Obsidian gives me some analogue patterns to the discussion in this article about "plugins versus composition" in #Neovim compared to #Kakoune.
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
#kakoune, #helix or #neovim ?
https://phaazon.net/blog/more-hindsight-vim-helix-kakoune
Interesting read by @phaazon
Best of all: he uses #bépo himself.
Despites @vjousse help, I’ve never been 100% satisfied by bépo/neovim to write fiction (instead of code). Maybe I should give kakoune or helix a try.
Anyone tried those?
About a decade ago I switched from Zsh to Fish. It was amazing: everything *just worked,* by default.
I'm getting the same feeling about Helix, coming from two decades of Vim.
Still adjusting to Kakoune-style modal editing, but everything else is great. It's fast, terminal-oriented, and has all the goodies (LSP, Tree Sitter, etc.) built-in.
Doing ARM assembly homework on my armhf pmOS device is so much fun. I managed to set up a very minimal dev environment with only #tcc + binutils + make + #kakoune , it's so smol.
If I have time I'd love to switch to doing it on the #NDS , I thiiink I could set up a simple "livecodeable" test harness, where I could just compile the assembly part (a single self contained function) and download it into a buffer and then call it via a function pointer.
#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
