dotfiles.cli VS waylock

I use about 12 plugins, most of which I've written myself.

bindkey -v is a builtin starting place, but there's a lot of extra bindings you can add to make it more like Vim. Personally, I've written a few plugins which make up the difference I want, and a few more personal bindings besides.

Here's my script. It forks off a playerctl --follow with a custom format to work around read skipping empty items (like a song without an artist). You don't have to do that, I just prefer that so I can add nwg-wrapper to view album art and song title on my desktop without spinning up another playerctl read loop.

Any config I write, I add to my dotfiles repo. Then I can clone it down whenever I'm setting up a new machine/reinstall

I wrote this script to run an arbitrary command when the provided app's window appears.

I'm curious; are you writing something like this?

Custom Powerlevel10k

Watch out for < and > too. Playerctl's command-line has specifiers for {{markup_escape(title)}}, I use it my playerctl segment. Here's how it looks with the custom CSS.

My full config is here, if you want to take a look at anything else, including the plugins I use.

There's also d and D which map to this function.

I meant that a standard of some sort is probably needed to handle both the desktop environment telling the display manager to lock the screen AND allowing said display manager to take over the screen and lock it. On Wayland at the moment I'm not aware of any screen locker that isn't part of the DE itself that works on GNOME or KDE (I only know of swaylock and waylock, and both require protocols that are only implemented by wlroots based compositors, at least according to Waylock's readme).

I only know about waylock, didn't try it though