zerocc

I prefer to use systemd-boot over grub - it's just so uncomplicated. As I dive deeper into btrfs, I see the desirability of snapshots, but no obvious tool or method for integration with my preferred boot-loader. I have never used rEFInd, or any other method, but I'd be willing to give them a go if necessary - anything but grub.

[running qtile - but I don't think that's important]

In the last few days I've picked up this unwanted behaviour: every time I move the cursor over a horizontal scroll bar. the bar will jerkily scroll to the right. And if I pass it over a dropdown menu, the menu contents will scroll wildly. Swapping mice makes no difference.

Using xev I have determined that the mouse is constantly sending a ButtonRelease event:

ButtonRelease event, serial 33, synthetic NO, window 0x2e00001,

root 0x297, subw 0x0, time 363519632, (388,154), root:(2327,203),

state 0x10, button 7, same_screen YES

I update every couple of days, but I didn't notice exactly when this behaviour first occurred.

HLWM noob here - bear with me!

I'm getting together a nice dzen2 script, and when run it renders a nice status bar on my first monitor. How do I direct it to do likewise on my second monitor?

Before now I've stuck to one TWM at a time - awesome, i3, bspwm, spectrwm - using startx to initiate a session.

I'm now running spectrwm as my main, all-purpose TWM, but I now I want to have Herbstluftwm as a secondary TWM, dedicated to one purpose (audio production).

I've installed TDM as a display manager. I had been using .xinitrc to autostart various things - picom, dunst, dropbox, wallpaper script, etc. But I have no need for those things in my audio environment. TDM provides a script for autostarting stuff in the same way, and I've shifted all the autostart items required by both WMs to there. This leaves the items I may want to opt out of - depending on WM - in .xinitrc for now...

Simple question: which window managers natively allow you to full-screen a window across two (or more?) monitors? I know i3 can do it - if it likes the drivers - and I managed to persuade bspwm to do it with a bit of scripting... Any other takers?

​

EDIT: I found Herbstluftwm

On my Arch installation I've been running ALSA/Jack - with no intervening pulseaudio - for some time. It suits my needs very well: I keep a Carla patchbay on a scratchpad (ie dropdown window) and patch connections by hand when needed. I prefer this to trying to make pulseaudio work for me.

So, my question is as stated in the title: what would pipewire give me that I don't already have - or didn't know that I wanted!

This may, or may not be of interest to you:

grep bind /path/to/spectrwm.conf | tail -n +3 |  sed 's/.....//;s/\]//' | column -t | dmenu -i -l 12 -p "Key Bindings"

The above command sends a nicely formatted list of all your keybindings to dmenu. Nothing is done with the selection - it's just a way of quickly reminding yourself. The list is in the same order as it appears in the ,conf file - so maybe you'd like to organise them into meaningful sections!

The tail command is needed because for some reason, grep appends a first line from somewhere before the first bind command - I have no idea why this happens and your mileage may vary. Adjust as needed.

I tried initially to assign the wh

I'm fresh to spectrwm (day two), and I'm struggling with how you define the window you want to add a quirk to - a hand, if you please:

On the particular window I'm playing with xprop | grep -E "^(WM_CLASS|_NET_WM_NAME|WM_NAME)"
returns

^(WM_NAME(STRING) = "Carla")

^(_NET_WM_NAME(UTF8_STRING) = "Carla")

^(WM_CLASS(STRING) = "carla-jack-multi", "Carla2-Multi-Client")

So how do I construct the definition?

I am using the jonaberg fork of picom, which provides, amongst other things, rounded corners for windows. Unfortunately, the spectrwm bar is also affected - an unwanted effect. How do I exclude the bar? I've tried using

rounded-corners-exclude = [ "window_type = 'bar'"]

and 'panel' to no effect. Any ideas?

Decided to experiment/play with spectrwm alongside my bspwm installation. However, logging in via LightDM takes me to a featureless desktop - except for whatever wallpaper I'm using on bspwm, for a few seconds, then takes me back to the logon screen...

What's happening?