<leon-p>
Nosrep: river sets the top/right/bottom/left tiled state for tiled windows. That is enough for normal gtk applications to not render shadows. but firefox isn't a normal gtk application. it does very cursed things, so it's not unexpected that it does weird things unfortunately
<leon-p>
that said, FF does behave correctly on my system
<Nosrep>
hmm
<Nosrep>
i checked with nwg-look and it does the same
<Nosrep>
maybe it has to do with rivercarro
<Nosrep>
or no if it's for all tiled windows then it should be okay
<Nosrep>
it does seem to be theme-dependent, adwaita is fine but breeze isn't
<Nosrep>
alright i can confirm adwaita has a shadow yet behaves properly
<Nosrep>
found it! adwaita has a case to disable shadow while maximized, breeze does not
<Nosrep>
that's odd, maybe i'll pr or something
Nosrep has quit [Ping timeout: 245 seconds]
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #river
_whitelogger has joined #river
soulseeder has left #river [#river]
soulseeder has joined #river
angry_vincent has joined #river
twelve has joined #river
twelve has quit [Remote host closed the connection]
Ireozar has quit [Read error: Connection reset by peer]
Ireozar has joined #river
<__toor__>
fleischie & leon-p what would be the solution to the GTK3 decorations for river? no solution available? would it help to upgrade to GTK4?
notzmv has quit [Ping timeout: 265 seconds]
<__toor__>
I want to summarize some possible "next step(s)" to the Zathura decoration issue over at github if there is anything that can be done to remove it or hide the decorations
<__toor__>
I have not been working with multiple screens in river. I typically never have a second screen attached. but now when I have that (setting up a demo environment for a due dilligence demo) I would like to map pins to specific outputs. Is that possible somehow?
<__toor__>
right now it seems like pins are global and outputs is a specific detail of the pins, quite the opposite to what I would like. Id rather see pins per output
<__toor__>
sorry, what am I talking about. Tried to reproduce it right now and then it worked exactly like I wanted it to work. LOL
<__toor__>
nevermind then. just works :)
<__toor__>
I guess I just need to find a tool to "switch output" without having to move the mouse cursor over to the other output
<LarstiQ>
__toor__: focus-output next/previous
twelve has joined #river
<__toor__>
map4 o to switch between outputs will be great. thanks!
_whitelogger has joined #river
Guest0 has joined #river
twelve has quit [Remote host closed the connection]
<fleischie>
__toor__: I don't know what is there to do. Maybe GTK4 has a mechanism to style and/or integrate the header bar into the client, but I don't know enough about GTK4.
Nosrep has quit [Ping timeout: 252 seconds]
angry_vincent has quit [Ping timeout: 245 seconds]
ramblurr has quit [Remote host closed the connection]
andycs0 has quit [Quit: I'm leaving, bzzZZzz!]
mekeor has joined #river
jjanzen has joined #river
jjanzen has quit [Client Quit]
Snetry has quit [Ping timeout: 248 seconds]
Snetry has joined #river
Guest43 has joined #river
Guest43 has quit [Client Quit]
mekeor has quit [Quit: towards emacs as interface to cybernetic council communism]
<leon-p>
__toor__: the proper solution is to patch gtk3 to support the proper protocol. isaac submitted a patch, but it never went through. one could try to pick that up
<leon-p>
I am actually not sure if this issue persists with gtk4, I don't think I've ever seen a gtk4 window that has a regular headerbar at all rather than the integrated header+tool-bar
jmilne224 has joined #river
<leon-p>
also I don't know what you mean by "pin", sorry