termite VS dunst

- you can also rectangular select like in vim, and then press either p (includes LF) or which joins the multiline clipboard text into a single line (removing LF's), that payed off a lot for output like `git status` and wanting to operate on parts of the output (files e.g.)

Have a look at the still young website's documentation here: https://contour-terminal.org/input-modes/#supported-text-obj...

for a more complete look of what you can do with the keyboard (normal mode) :)

[1] https://github.com/thestinger/termite/

Also, regarding VTE, the author of termite (discontinued terminal emulator) expressed similar concerns about the GNOME devs. Apparently, they have little interest in making the library useful to people not working on GNOME apps: https://github.com/thestinger/termite

Termite is obsolete by Alacritty.

I simply do not want to use anything libvte based. And that's what sakura is and termite used to be.

History and experience tells a different story [1]. Never trust a library that is maintained by GNOME.

1.: https://github.com/thestinger/termite

This post by the Termite developer, with respect to VTE, is quite instructive

> https://github.com/thestinger/termite/blob/master/README.rst...

Wow, this confirms a lot of my impressions:

>> In 2012, we submitted a tiny patch exposing the APIs needed for the keyboard text selection, hints mode and other features. Despite support from multiple other projects, the patch was rejected. It's now almost a decade later and no progress has been made. There is no implementation of these kinds of features in VTE and it's unlikely they'll be provided either internally or as flexible APIs. This is the tip of the iceberg when it comes to their hostility towards other projects using VTE as a library. GTK and most of the GNOME project are much of the same. Avoid them and don't make the mistake of thinking their libraries are meant for others to use.

This is exactly why sixel-tmux exists as a separate entity!

> Yeah, I read the entire conversation and if sixel support lands in tmux upstream, it would indeed be good news.

I'll keep my fingers crossed, but right now, there seems to be a lot of good will. I will do everything I can.

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.