<plumeus>
Doesn't `dunst` support Wayland natively too?
<plumeus>
I personally use `mako`.
notzmv has quit [Ping timeout: 250 seconds]
mx08 has quit [Quit: WeeChat 3.0]
mx08 has joined #river
snakedye has joined #river
Guest8363 has joined #river
notzmv has joined #river
Guest8363 has quit [Quit: Client closed]
StopNGo has joined #river
lbia has quit [Quit: lbia]
lbia has joined #river
Ordoviz has quit [Ping timeout: 265 seconds]
talismanick has quit [Ping timeout: 244 seconds]
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
elshize has joined #river
Ordoviz has joined #river
lbia has quit [Quit: lbia]
lbia has joined #river
waleee has joined #river
jao has joined #river
fitrh has joined #river
fitrh has quit [Quit: fitrh]
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #river
ayushnix has joined #river
ayushnix has quit [Changing host]
jao has quit [Remote host closed the connection]
jao has joined #river
clippy has joined #river
<clippy>
Is it possible to execute multiple configuration commands in one riverctl command? Spawning a riverctl process for each config entry seems expensive
<leon-p>
no, it's not
<leon-p>
however if you are concerned about efficiency, you can write a river config in a language that has some Wayland implementation. Then you can connect to the server only once and send all configuration over a single connection.
<clippy>
Thank you that sounds good. It's nice that the init fille is merely an executable
elshize has quit [Ping timeout: 252 seconds]
elshize has joined #river
clippy has quit [Ping timeout: 252 seconds]
ayushnix has quit [Remote host closed the connection]