cyph3r has quit [Read error: Connection reset by peer]
jao has joined #river
elshize has joined #river
cyph3r has joined #river
cabal704 has joined #river
Ordoviz has quit [Ping timeout: 252 seconds]
cabal704 has quit [Ping timeout: 244 seconds]
cabal704 has joined #river
ayushnix has joined #river
ayushnix has joined #river
ayushnix has quit [Changing host]
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #river
elshize has quit [Ping timeout: 252 seconds]
elshize has joined #river
waleee has quit [Ping timeout: 268 seconds]
Ordoviz has joined #river
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #river
Ordoviz has quit [Ping timeout: 244 seconds]
Ordoviz has joined #river
ayushnix has quit [Remote host closed the connection]
zdykstra1 is now known as zdykstra
ayushnix has joined #river
cabal704 has quit [Quit: WeeChat 3.5]
elshize has quit [Ping timeout: 265 seconds]
ayushnix has quit [Changing host]
ayushnix has joined #river
waleee has joined #river
cabal704 has joined #river
cabal704 has quit [Ping timeout: 244 seconds]
cabal704 has joined #river
cyph3r has quit [Ping timeout: 252 seconds]
Ordoviz has quit [Ping timeout: 265 seconds]
waleee has quit [Ping timeout: 252 seconds]
jao has quit [Remote host closed the connection]
Nulo has quit [Read error: Connection reset by peer]
Nulo has joined #river
jao has joined #river
<jao>
hi. is there a workaround for getting rid of the window title bar for pgtk emacs?
<tleydxdy[m]>
I think you'll need to patch gtk
<jao>
oh my
<tleydxdy[m]>
there's an open mr on their gitlab, but last activity was 9 month ago I think
<jao>
i just saw it
<jao>
pity, this is really a showstopper for me. i'm in emacs 95% of the time, and the bar is a nuisance
<jao>
(petty complain, i know)
Guest7555 has joined #river
Guest7555 has quit [Client Quit]
waleee has joined #river
jao has quit [Remote host closed the connection]
jao has joined #river
jao has quit [Remote host closed the connection]
Ordoviz has joined #river
jao has joined #river
<leon-p>
jao: I have a patch for that (played around with pgtk emacs a few months ago), give me a minute I'll dig it up
<jao>
leon-p, oh, excellent!
<leon-p>
probably won't apply cleanly against master, but it's simple so I recommend just doing it manually: https://paste.rs/pmR
<cabal704>
I don't know why, but river draws the top bar of zathura, while using "cage -d zathura" it disappears... -d=Don't draw client side decorations when possible
<cabal704>
I tried using csd-filter but nothing happened
<leon-p>
cabal704: that's because GTK uses an old protocol for negotiating SSD vs CSD which river des not implement (on purpose)
<jao>
leon-p, thanks, that's simple, yes.
<jao>
another little glitch is that emacs alpha frame transparency doesn't seem to be working. is there an app independent way of setting opacity in river(ctl)?
<cabal704>
leon-p: I got it, thanks!
<leon-p>
no, we had opacity once but removed it for now. eye candy isn't the focus right now
<leon-p>
it may come back, we have no hard stance against fancy things - unlike other compositors - but I don't know when and in what form
<jao>
okay, fair enough
<jao>
just curious: how come sway manages to get rid of decorations in emacs/zathura? does it implement the old protocol?
<leon-p>
from what I remember from emacs rendering model however is that it uses a cairo context over a GTK window, meaning you'd have to set opacity in both with is probably buggy right now
<leon-p>
jao: yes, swayy implements the old protocol
<jao>
(i just notice however that foot's opacity control works, so there must be a way of doing this independently)
<jao>
i see
<leon-p>
when a client sets its own opacity, river is not involved. the client just choses to render with a different alpha to its buffer
<leon-p>
there is a difference between client side and server side opacity
<jao>
then there must be something wrong in how emacs implements its opacity
<leon-p>
you can try to hack in some CSS for the emacs windows to set the opacity
<jao>
you mean as a gtk theme?
Ordoviz has quit [Quit: WeeChat 3.6]
<leon-p>
kinda. themes are just monkey-patches to GTKs internal CSS things
<leon-p>
however a program can also set CSS properties of GTK
<jao>
(although again, client-side opacity for emacs seems to work fine in sway)
<jao>
ah, how would that work (roughly)? my experiences with themes are not good
<leon-p>
from memory: you find where the GTK windows are created in code, there you create youg CSS settings as a string, create a provider from that and apply it to the window
<jao>
okay
<jao>
emacs pgtk sets its alpha with a call to gdk_window_set_opaque_region(); maybe another old protocol kind of thing
<leon-p>
nope, thats client side
<leon-p>
there is no protocol dealing with opacity
<leon-p>
if a client wants something to be transparent, it just renders it transparent
<leon-p>
(server side opacity isn't really a thing a server is supposed to do. it falls in the same category as rotating windows: technically possible but not really useful)
<leon-p>
but as I said, pgtk emacs does not use GTK to actually render. I uses cairo IIRC. So even if the gtk window is transparent, there is a cario context over it that may not be
<jao>
so for some reason that gdk call is not working when emacs runs under river, while it does when it runs under sway.
<leon-p>
what's the emacs function I can call from M-x so I can test it real quick?
<jao>
maybe i'm doing something else differently, like the way i set the wallpaper or something like that, that has that side-effect. as you say, it seems all client side, so river should make not difference
<jao>
leon-p, just set the frame parameter alpha-background to the opacity
<leon-p>
is that an arg to make-frame? (I am not an emacs user, btw)