<tleydxdy[m]>
ifreund: the sigpipe fix is ready, yay
vertical24 has joined #river
<vertical24>
hello, was wondering if there is a way to have the views/tags preserved when my monitors go into standby?
<vertical24>
i notice that when i turn them back on, all of my views are on my primary monitor
<vertical24>
and i have to go back and move everything over each time
<vertical24>
ok i have discovered 'wlopm' which looks like it should do the trick. but it doesn't seem to work
<vertical24>
upon turning my monitors back on, all of them still end up on the primary monitor
<vertical24>
maybe it has something to do with my machine using a mix of HDMI and DP
<vertical24>
the views always seem to jump to the HDMI whenever the monitors go off
<leon-p>
vertical24: wlopm doesn't turn off the logical output, it just tells river to stop displaying it. That is why your windows are still on it. When actually disabling an output, the windows on it get evacuated to still existing outputs and right now we don't store what outputba window was on originally.
<vertical24>
leon-p: i'm not doing anything to specifically disable the output though?
<vertical24>
wlopm seems to work on my machine with an nvidia card, which has 2x display port
<vertical24>
(using the same monitors)
<vertical24>
so on my nvidia gpu (2x display port), turning off the monitors with wlr-randr moves all views to one display, but turning them off with wlopm works perfectly and all views retain their positions
<vertical24>
on my intel gpu (1x hdmi, 1x display port) both wlr-randr and wlopm has all views move to one display
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 268 seconds]
wrkzk has joined #river
snakedye has quit [Ping timeout: 268 seconds]
kitty4 has quit [Ping timeout: 268 seconds]
kitty4 has joined #river
wrkzk has quit [Read error: Connection reset by peer]
wrkzk has joined #river
wrkzk has quit [Client Quit]
wrkzk has joined #river
wrkzk has quit [Quit: WeeChat 3.6]
gwizon has joined #river
<dnkl>
I'm having an issue where a key combo that used to work no longer is. Not sure if it's a river issue, or something else in the system...
<dnkl>
if libinput debug-events doesn't print anything on a key press, could that be river's fault? Or should I go look elsewhere?
<dnkl>
I think we can ignore my question :)
<dnkl>
pretty sure I mis-remembered
<dnkl>
the combo has never worked for me (on my laptop), and I think it's the keyboard itself that is to blame
<n0r>
Its very annoying that some 3-button-combinations physically can't work on some keybords, yeah. On mine Caps+Shift+X is such an example, which I would really like to use...
<leon-p>
to be fair, I think most engineers designing laptop keyboards don't consider capslock to be a key that is often pressed, let alone in combination with others, so if you already know your board has limitations, it makes sense to put them were most users will never encounter them