<Guest35>
I am wondering what is the best way to autostart programs, such as kanshi
<Guest35>
Currently, I have something like riverctl spawn 'wlr-randr --output eDP-1 --mode 2560x1600 120 Hz --scale 1.3' in my init file for river
<Guest35>
It works, but I would like to know best practices
<Nulo>
Guest35, AFAIK that's best practice
<Guest35>
I see, thanks!
snakedye has quit [Ping timeout: 245 seconds]
<anb1>
Guest35: I put these screen related stuff in kanshi, so it runs when screen changes
Guest8688 has joined #river
Guest8688 has quit [Client Quit]
waleee has quit [Ping timeout: 260 seconds]
funcfun has joined #river
Guest35 has quit [Quit: Client closed]
_whitelogger has quit [Ping timeout: 268 seconds]
_whitelogger_ has joined #river
wrl has quit [Ping timeout: 260 seconds]
noopdecoder has quit [Ping timeout: 260 seconds]
kennylevinsen has quit [Ping timeout: 260 seconds]
dbuckley has quit [*.net *.split]
travankor has quit [*.net *.split]
notzmv has quit [*.net *.split]
ecocode__ has quit [*.net *.split]
Nulo has quit [*.net *.split]
Misthios has quit [*.net *.split]
dnkl has quit [*.net *.split]
romangg has quit [*.net *.split]
st4ll11 has quit [*.net *.split]
qyliss has quit [*.net *.split]
anb1 has quit [*.net *.split]
yyp has quit [*.net *.split]
tdeo has quit [*.net *.split]
ChanServ has quit [*.net *.split]
aruhier has quit [*.net *.split]
priner has quit [*.net *.split]
_whitelogger has quit [*.net *.split]
emersion has quit [*.net *.split]
entenel has quit [*.net *.split]
occivink has quit [*.net *.split]
dagle has quit [*.net *.split]
funcfun has quit [*.net *.split]
hspak has quit [*.net *.split]
sjtio has quit [*.net *.split]
anubhavkini has quit [*.net *.split]
pedrohlc[m] has quit [*.net *.split]
edrex[m] has quit [*.net *.split]
msiedlaczekelshi has quit [*.net *.split]
ifreund has quit [*.net *.split]
voroskoi[m] has quit [*.net *.split]
inclemen1 has quit [*.net *.split]
zxtx has quit [*.net *.split]
_whitelogger has joined #river
priner has joined #river
<ifreund>
Nulo: running wlr-randr in the init file is racy actually, I'd consider kanshi best practice for persistent output config
romangg has quit [*.net *.split]
st4ll11 has quit [*.net *.split]
qyliss has quit [*.net *.split]
anb1 has quit [*.net *.split]
yyp has quit [*.net *.split]
ChanServ has quit [*.net *.split]
priner has quit [*.net *.split]
kennylevinsen has quit [*.net *.split]
tdeo has quit [*.net *.split]
aruhier has quit [*.net *.split]
occivink has quit [*.net *.split]
entenel has quit [*.net *.split]
dagle has quit [*.net *.split]
hspak has quit [*.net *.split]
sjtio has quit [*.net *.split]
anubhavkini has quit [*.net *.split]
pedrohlc[m] has quit [*.net *.split]
edrex[m] has quit [*.net *.split]
dbuckley has quit [*.net *.split]
travankor has quit [*.net *.split]
notzmv has quit [*.net *.split]
ecocode__ has quit [*.net *.split]
Nulo has quit [*.net *.split]
Misthios has quit [*.net *.split]
dnkl has quit [*.net *.split]
pkap has quit [*.net *.split]
noopdecoder has quit [*.net *.split]
novakane has quit [*.net *.split]
msiedlaczekelshi has quit [*.net *.split]
ifreund has quit [*.net *.split]
inclemen1 has quit [*.net *.split]
zxtx has quit [*.net *.split]
voroskoi[m] has quit [*.net *.split]
ChanServ has joined #river
notzmv has joined #river
sjtio has joined #river
priner has joined #river
pedrohlc[m] has joined #river
edrex[m] has joined #river
anubhavkini has joined #river
entenel has joined #river
voroskoi[m] has joined #river
msiedlaczekelshi has joined #river
hspak has joined #river
<Nulo>
ifreund, how is it racy? Still, I was talking about running daemons in general
snakedye has joined #river
leon-p has joined #river
<ifreund>
Nulo: river starts execution of the init file before outputs are created
<ifreund>
so there's a chance that there will not yet be any outputs at the time wlr_randr is run
<ecocode__>
that is weird ...
<ecocode__>
So where should I start apps that require outputs to be already created ?
<ecocode__>
like waybar
<ifreund>
ecocode__: I don't think waybar requires outputs to be created before it starts, it will just wait until they are created
<ifreund>
wlr-randr however will exit with an error if the output you try to configure doesn't exist at the point in time when it checks
<ecocode__>
is there some hook that tells when an output is created ?
<ecocode__>
or destroyed ?
<ecocode__>
i guess this is done by wlroots
<ifreund>
wayland clients recieve wl_registry.create and wl_registry.destroy events when outputs are created/destroyed
<ifreund>
kanshi provides a way to run an arbitrary command when a certain output configuration is matched iirc
<ecocode__>
awesome ! thx for that info
novakane has joined #river
snakedye has quit [Ping timeout: 264 seconds]
snakedye has joined #river
waleee has joined #river
FollieHiyuki has joined #river
FollieHiyuki has quit [Quit: FollieHiyuki]
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 265 seconds]
snakedye has joined #river
<Nulo>
Okay, the segfault that I had before happens when calling `riverctl exit`
<Nulo>
Exit by segfaulting :P
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
<ifreund>
Nulo: are you able to reliably reproduce? I can't
<Nulo>
Yes, every time. I'll try to get a backtrace when I can get Alpine to give me a core dump
<Nulo>
I'm dealing with a Let's Encrypt expiration dumpster fire right now
<ifreund>
you don't really need that, just build river in debug mode and redirect all of stdout and stderr to a file
<ifreund>
have fun with that dumpsterfire for now though :P
<Nulo>
Trying to prove to a client that half the internet uses Let's Encrypt and they really should upgrade instead of telling us to buy a certificate for them...
<Nulo>
Oversharing in IRC is my passing. Although I assume it's the experience of way too many folks