ChanServ changed the topic of #river to: river - a dynamic tiling Wayland compositor || https://codeberg.org/river/river || channel logs: https://libera.irclog.whitequark.org/river/
mtm has quit [Ping timeout: 272 seconds]
mtm has joined #river
waleee has quit [Ping timeout: 256 seconds]
Snetry has quit [Ping timeout: 264 seconds]
Snetry has joined #river
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 268 seconds]
Palanix_ has joined #river
Palanix has quit [Ping timeout: 246 seconds]
Palanix_ is now known as Palanix
ninewise has quit [*.net *.split]
sadparadise has joined #river
ninewise has joined #river
<sadparadise> hello, people. i've read about the idea of separing the window management part from the rest of river and i think it's a very interesting thing, but please help me understand something: will it be possible for developers of window managers that will work with river to implement manual tiling, like the one from sway?
<sadparadise> *separating
groknull has joined #river
groknull has quit [Remote host closed the connection]
angry_vincent has joined #river
chipps has quit [Server closed connection]
chipps has joined #river
ptrckd has quit [Server closed connection]
ptrckd has joined #river
chipps has quit [Ping timeout: 258 seconds]
chipps has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
upsala has joined #river
<upsala> I have a question regarding window rules. I am using LibreWolf/Firefox and the bitwarden extension. When I press ctrl+shift+L the popup where I put in the masterpassword gets tiled, which feels awkward. `lswt` returns '----     LibreWolf   "Extension: (Bitwarden Password Manager) - Bitwarden — LibreWolf" '. To my knowledge 'riverctl
<upsala> rule-add -app-id "LibreWolf" -title "Extension: (Bitwarden Password Manager) - Bitwarden — LibreWolf" float' should work for this right? It doesn't though. Any ideas?
<NickH> sadparadise: others will confim, but yes I believe so.
<NickH> As I understand it, it should allow people a lot freedom (and with most of the heavy lifting done by river) to write WMs for river just like they did for X.
Franciman has joined #river
alexherbo2 has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
<novakane> upsala: iirc Firefox changes the title after the creation of a popup
angry_vincent has joined #river
<upsala> that is not cool, any way to work around that?
<ifreund> upsala: lswt has a cli Option to run indefinitely and log changes
<ifreund> Start that and then open the popup while its running
<upsala> yeah I think this just doesn't work, first title is (null) and then the title changes twice. The (null) title is the same for every LibreWolf window unfortunately
<upsala> Sorry I meant the first title is "LibreWolf" and then it gets changed to something extensionspecific
angry_vincent has quit [Read error: Connection reset by peer]
angry_vincent has joined #river
ccha has joined #river
upsala has quit [Ping timeout: 256 seconds]
angry_vincent has quit [Ping timeout: 245 seconds]
alexherbo2 has quit [Ping timeout: 256 seconds]
occivink has quit [Server closed connection]
occivink has joined #river
adv8tor has joined #river
angry_vincent has joined #river
mtm has quit [Ping timeout: 264 seconds]
mtm has joined #river
<sewn> this program seems to make river crash:
<sewn> i'm not exactly sure if it was a good idea to make it crash
<ifreund> sewn: river should never crash, every crash is a bug
<ifreund> are you testing river's master branch or some other version?
<sewn> river 0.3.3
<sewn> ill test master
<sewn> fails in master
<sadparadise> NickH: that would be one of the coolest things to happen in the world of wayland compositors...
<sadparadise> thank you, btw.
<ifreund> sewn: fwiw that client is committing a protocol error
<ifreund> river still shouldn't crash though ofc
<sewn> yep
<sewn> the protocol requires that unlock_and_destroy only be called if locked event was sent by compositor, otherwise use only destro
<sewn> y
<ifreund> sewn: the protocol actually doesn't allow the client to destroy the object until either locked or finished is sent
<sewn> ah
Guest66 has joined #river
<Guest66> Hello, I'm trying out river, and was wondering what the correct way to autostart programs from river/init
<Guest66> is it backgrounding the proccess? or using riverctl spawn?
<ifreund> backgrounding the process is a fine way to do that
<ifreund> riverctl spawn only really exists to allow spawning stuff from mappings
<Guest66> Alrighty
<adv8tor> Is there a way to focus the main window when the currently active window is closed?
The_Buhs has quit [Quit: Ping timeout (120 seconds)]
The_Buhs has joined #river
waleee has joined #river
Guest66 has quit [Quit: Client closed]
angry_vincent has quit [Remote host closed the connection]
adv8tor has quit [Ping timeout: 258 seconds]
waleee has quit [Ping timeout: 258 seconds]
agz has joined #river
mohan43u has quit [Quit: WeeChat 4.3.3]
agz has quit [Quit: leaving]
catman has quit [Ping timeout: 256 seconds]
siaal has quit [Remote host closed the connection]
siaal has joined #river
_whitelogger has quit [Server closed connection]
_whitelogger has joined #river
travankor has quit [Server closed connection]
mohan43u has joined #river
maxsch has quit [Remote host closed the connection]
AlxFG has quit [Remote host closed the connection]
fossdd_ is now known as fossdd
sewn has quit [Remote host closed the connection]
AlxFG has joined #river
sewn has joined #river
maxsch has joined #river
upsala has joined #river
u0_a226 has joined #river
sadparadise has quit [Ping timeout: 264 seconds]