rofi VS picom

You'll probably like rofi.

Also, I use this script so that Rofi will show my clipboard instead of the native klipper UI (because it's far less keyboard friendly). Normally the script works great, but the script chokes whenever I `dd` an empty line or a lone `\`, putting an empty entry on my clipboard, which the wrapper than assumes means I'm at the end of the list of clipboard entries.

Which rofi you run? The original one from https://github.com/davatorium/rofi (which is Xorg base, so it has to start XWayland) or the Wayland-based fork on https://github.com/lbonn/rofi?

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

I like rofi (super flexible, i also use it as a custom alt-tab option in openbox) and wofi is a nice option on wayland

Modi are covered in the documentation. They set what Rofi displays in its window. You can run Rofi from a keybind, or a module in Polybar, or by using click handlers. Extremely extensible and versatile. And a shit ton of fun to theme. :)

xwinmosaic: Having tried XMonad.Actions.GridSelect in the past, I found the 2-dimensional grid more confusing than useful because you cannot intuit where it would lay things out. I find Rofi to be more usable for window switching because it prioritizes text filtering. https://github.com/davatorium/rofi

(https://github.com/yshui/picom/blob/next/picom.sample.conf)

Also I took a census and zero founding members of NWA are "straight outta Picom". That's right, you heard it here first: Not even MC Ren is running Picom.

Update: after reporting in picom GitHub repo this is temporarily solved by using --no-frame-pacing. Looks like a recent commit causes this. You can view the discussion here: https://github.com/yshui/picom/issues/1072

NEED HELP TESTING (write your issues here): https://github.com/yshui/picom/issues/1052

Compositor : picom

It looks like this was identified and the repo corrected in Jan (https://github.com/yshui/picom/issues/808) but the NixOS package has not been updated since Nov.

If you have compositing you are likely using picom. You can check if it's running with ps -A | grep picom. I've never dealt with this issue as I don't really game on linux often, but I'm sure there's a solution somewhere in the github docs or issues. Worst case scenario you could always just kill the process with killall picom whenever you're about to game, and re-enable it with picom -b after. Do note though that currently running windows might bug out a bit when you kill/start the compositor.

Picom is broken for me with GLX backend related Github issue.