<chipps>
how can I specify a certain screen resolution for river to run on?
<chipps>
do I just add the command to the .config/river/init file, or is there some "better" way of doing it?
waleee has quit [Ping timeout: 256 seconds]
<ifreund>
chipps: I'd recommend using kanshi for that
travankor has quit [Ping timeout: 240 seconds]
travankor has joined #river
travankor has quit [Ping timeout: 240 seconds]
<chipps>
ifreund: thanks!!!
notzmv has quit [Ping timeout: 240 seconds]
Guest78 has joined #river
Guest78 has quit [Client Quit]
snakedye has quit [Ping timeout: 256 seconds]
snakedye has joined #river
notzmv has joined #river
<leon-p>
in command/filter.zig on line 54, aren't we leaking memory? the description of getOrPut() says "caller should then initialize the value (but not the key)"
<ifreund>
leon-p: pretty sure that code is fine, the reason I wrote it that way is to avoid duping the key memory if there is already an existing entry in the hash map
<ifreund>
the key we pass to getOrPut() is owned by the code in Control.zig and will be freed after the command function is run
<ifreund>
so we need to dupe the memory for the key that is stored in the hashmap
<ifreund>
we free all the keys in Config.deinit()
<leon-p>
ah, I see, that makes sense
bsdeedee[m] has joined #river
beeSD has joined #river
<ifreund>
with the wlroots and zig updates done, I think my next focus for river will be migrating to the wlroots scene graph API and refactoring
<beeSD>
Hello, when I go to run river I am met with an, error: failed to run init executable /home/me/.config/river/init: FileNotFound
<ifreund>
once that's done, prototyping for the view management protocol should be more feasible
<ifreund>
beeSD: well, did you read the documentation and create an init script?