<IchikaZou>
Just fully setup River, the usability is surprisingly great. The work flow I have on sway are able to fully reproduce in River(in some part it’s even better than sway)
angry_vincent has joined #river
angry_vincent has quit [Changing host]
angry_vincent has joined #river
eShaev9z has quit [Ping timeout: 248 seconds]
eShaev9z has joined #river
IchikaZou has quit [Remote host closed the connection]
IchikaZou_ has joined #river
IchikaZou_ has quit [Remote host closed the connection]
IchikaZou has joined #river
waleee has quit [Ping timeout: 252 seconds]
dbuckley has quit [Ping timeout: 260 seconds]
IchikaZou has quit [Read error: Connection reset by peer]
IchikaZou has joined #river
muirrum has quit [Ping timeout: 252 seconds]
muirrum has joined #river
angry_vincent has quit [Ping timeout: 248 seconds]
angry_vincent has joined #river
angry_vincent has quit [Changing host]
angry_vincent has joined #river
IchikaZou has quit [Remote host closed the connection]
IchikaZou has joined #river
Szadek has quit [Quit: WeeChat 3.8]
hendry has joined #river
hendry has quit [Client Quit]
<ifreund>
nice to hear that river's working out well for you :)
Szadek58 has quit [Ping timeout: 248 seconds]
<andrea>
been running river master (updater after the scene graph merge) all night (literally) while writing my thesis. non a single bug encounteded.
<andrea>
s/non/not/
<andrea>
s/encounteded/encountered/
<ifreund>
nice :)
IchikaZou has quit [Remote host closed the connection]
IchikaZou has joined #river
IchikaZou has quit [Remote host closed the connection]
taupiqueur1 has quit [Ping timeout: 255 seconds]
fitrh has joined #river
fitrh has quit [Client Quit]
fitrh has joined #river
<fitrh>
After scene graph is merged, it seems that mako margin config has no effect
<fitrh>
Is this river issue or mako?
<leon-p>
seems to be working for me
<fitrh>
Yeah, after recompiling, it works
<fitrh>
Oh, but it's now displayed on top of yambar
angry_vincent has quit [Remote host closed the connection]
talismanick has joined #river
Szadek581 has joined #river
Szadek581 has quit [Quit: off]
talismanick has quit [Ping timeout: 260 seconds]
<ifreund>
hmm, maybe I messed up the exclusive zones
Han has joined #river
Han has quit [Ping timeout: 255 seconds]
Han has joined #river
<Han>
What am I missing here? ./build.zig:129:13: error: no member named 'source' in struct 'std.build.Pkg'
<ifreund>
Han: probably the wrong zig version for the river version you are trying to build
<ifreund>
what river version are you building?
<Han>
Ah, zig-0.9.1, when I need 0.10, yes you are right.
Gozenka has joined #river
<Han>
:190:9: error: zig-wlroots requires wlroots version 0.16 I have 0.17.0-dev, straight from git.
<waleee>
Han: wlroots is not always backwards compatible
<waleee>
you could do a hacky workaround to use your master branch wlroots but it's not guarenteed to work
<Han>
Or install 2 wlroots versions.
<waleee>
or that yes
<Han>
How can I tell zig where to find the right wlroots version?
<waleee>
fun stuff involving pkg-config I think
<waleee>
or manually change some stuff in river's build.zig
Gozenka has quit [Quit: Client closed]
<waleee>
Han: honestly the least hassle way would be to uninstall 0.17-dev and checkout the 0.16 branch of wlroots and build that
<waleee>
*install that
<leon-p>
C_INCLUDE_PATH, PKG_CONFIG_PATH, LD_LIBRARY_PATH should be a good start
<leon-p>
behold: madness awaits
<Han>
I just did, luckily sway builds against 0.16
<waleee>
there's no applications that would require 0.17 since it's not released yet
<Han>
Oops, no it does not.
Gozenka has joined #river
<ifreund>
yeah, sway master tracks wlroots master
<ifreund>
sway makes vendoring wlroots a bit easier than river does currently as you can use a meson subproject instead of the PKG_CONFIG_PATH pain
<Gozenka>
Hi! I really like River, as I could not use Sway's i3 style coming from dwm. Sadly, I have some weird issues with Chromium.
<Gozenka>
River crashes 90% of the time when I exit chromium. Also dialog windows are not coming up floating, but as tiled windows.
<Gozenka>
I'm going to try and get some logs for the crash if you are interested.
<Gozenka>
Chromium is in Wayland mode.
<leon-p>
what river version are you using?
<Gozenka>
Also HW Video Acceleration is not working, while it worked in Xorg. I tried all the options I could. But this is no big deal. I know HWAccel is quite buggy with Chromium in general.
<novakane>
ifreund: ah right, my bad, I'm on my phone and that is pretty shitty to look at code/log lol
<ifreund>
no worries!
<waleee>
Han: but of course what ever floats your boat :)
<Han>
it really floats my boat.
<ifreund>
anyone know off the top of their head how I can make chromium use its wayland backend so I can reproduce Gozenka's bug?
<Gozenka>
--ozone-platform=wayland
<Gozenka>
--enable-features=UseOzonePlatform
<Han>
ifreund, thanks for the heads up. I switched back to sway for now. I'll probably take another stab at river soonish.
<Gozenka>
it happens 90% of the time after using the browser for a while, but at fresh startup I have to do a bunch of stuff and try a few times to reproduce it
<Gozenka>
those in: ~/.config/chromium-flags.conf
<ifreund>
Gozenka: just passing them on the command line seems to have done the trick, thanks
<Gozenka>
I pretty much tried disabling all my flags too, so I doubt it is about my other flags.