kakoune VS dunst

Helix's modal editing is based on Kakoune's modal editing which is like an evolution to Vim's modal editing. You can think of it as being always in selection (visual) mode. https://github.com/mawww/kakoune?tab=readme-ov-file#selectio...

And while it doesn’t use the sam language precisely, I think in the broader “postfix Vi with visual feedback” category Kakoune[1] also warrants mentioning. The command language, in my experience, feels much more logical than that of Vis coming from a blank slate (things might be different if you come from Vim, but even when I used Vim regularly I never used the editing language that much exactly because I could never remember the damn thing).

And having mentioned Kakoune it’d probably be unfair to then not mention Helix[2]. It has a very similar editing language, but it’s a fairly anti-Unix everything-bolted-in affair on the inside (“everything works out of the box” being the advertising take) compared to Kakoune’s Acme-inspired no-scripting scripting (there’s an ex-style command to exec a user program that can then drive the editor over stdio RPC, a set of hooks, and that’s it). So if you’ve come for the Plan 9 feels, I don’t expect Helix to be that appealing. It’s still a good editor, nevertheless.

[1] https://kakoune.org/

[2] https://helix-editor.com/

You can take a look at kakoune. The source code (excluding documentations, test cases, customizations etc.) is less than 40k. It is, IMHO, a show case of a C++ project in use.

> I wonder if the author has ever heard of vis[0]

Yes.

https://github.com/martanne/vis/wiki/Differences-from-Kakoun...

https://github.com/mawww/kakoune/wiki#onboarding

> which imho fulfills far better each one of those premises

Not very motivated for such a harsh critic..

I've been using Vim for years, but if there was one thing I could change, it would be the verb-noun order. The Kakoune[1] editor behaves mostly like Vim, but where Vim has `dw` as "delete word", Kakoune has it backwards: `wd`.

It might sound minor, but by placing the range first, Kakoune can give a preview of what will be changed. The longer or more complicated the command, the more this feature shines.

Strictly better as far as I know. A shame my muscle memory, and all default installations, are still stuck with Vim.

[1] https://kakoune.org/

Helix is a postmodern text editor built in Rust built for the terminal. It is inspired by Kakoune, another Rust based text editor. Helix has got multiple selections, built-in Tree-sitter integration, powerful code manipulation and Language server support.

OS: Arch Linux WM: Qtile Panel: Qtile bar Launcher: Rofi Notification Daemon: Dunst Terminal: Alacritty Shell: Zsh Compositor: Picom File Manager: Nemo Music Player: Spotify & ncmpcpp

https://github.com/dunst-project/dunst is a pretty popular notification daemon that comes to mind.

Notification : dunst

Your notifications are not provided by Plasma, but by dunst. Either you installed dunst yourself or something else you installed is dependent on dunst.

Are you running something able to act on notification requests from programs, e.g. dunst (which is what i use)?

OS: Arch Linux WM: Bspwm Compositor: Picom Launcher/Powermenu: Rofi Status Bar: Polybar Terminal: Alacritty Shell: Zsh Editor: Neovim Notification: Dunst File Manager: Lf PDF Viewer: Zathura Text fonts: JetBrains Mono Nerd Font DOTFILES: here

Here's the documentation to create an asynchronous monitor with pyudev. When a device is plugged in, use subprocess to run notify-send and send a notification through dunst with the proper parameters (search "do_action" in the dunst docs), so for example you can bind your left click to mount and your middle click to mount and open

The notification in your screenshot looks like dunst. Removing that notification server should bring back the default notifications by Cinnamon's own notification server (which, AFAIK, is built-in).

You can use dunst for notifications, minimal and lightweight. I use it for my volume and brightness control along with sxhkd. dunst Hope this helps.