sjtio has quit [Quit: Bridge terminating on SIGTERM]
keithhub[m] has quit [Quit: Bridge terminating on SIGTERM]
edrex[m] has quit [Quit: Bridge terminating on SIGTERM]
priner has quit [Quit: Bridge terminating on SIGTERM]
anubhavkini has quit [Quit: Bridge terminating on SIGTERM]
pltrz has quit [Quit: Bridge terminating on SIGTERM]
sjtio has joined #river
priner has joined #river
anubhavkini has joined #river
keithhub[m] has joined #river
edrex[m] has joined #river
pltrz has joined #river
snakedye has joined #river
ext0l has quit [Ping timeout: 240 seconds]
novakane has quit [Read error: Connection reset by peer]
novakane_ has joined #river
<ifreund>
dagle: hrm, I just updated waybar and noticed the tags lagging way behind
<ifreund>
I think that's a waybar regression :/
<ifreund>
I'm sick of waybar's complexity though tbh, I'll probably try and switch to yambar or something else on my desktop
<novakane_>
ifreund: with your simple setup yambar would be good, I don't know how many bar have river supports
<ifreund>
I'm willing to add river support to any good bar that's out there
<ifreund>
(working on updating waybar for your xdg-activation changes, and fixing a few bugs along the way right now)
<ifreund>
once I've got that done and tested I'll merge
<novakane_>
time to make your own bar then :P
<novakane_>
nice!
<ifreund>
well the thing is, I don't have time to do that :P
<novakane_>
well you could stop sleeping and you'll have more time in a day, simple :P
leon-p has joined #river
<snakedye>
Brilliant idea
<dagle>
ifreund: Yes, I found it to be worse after an update too, didn't notice it before.
<dagle>
And I'm using waybar because it works and the example config was close to what I wanted (after removing some stuff) and I haven't bothered since.
<dnkl>
Xdg-activation! Woot!
<ifreund>
\o/
<ifreund>
dagle: by the way, I fucked up forward compatibility when I wrote the original waybar river support, so Waybar is broken on master river currently :/
<ifreund>
(and you probably should hard code the other wl_registry_bind() calls as well)
<dnkl>
ifreund: learnt the hard way... (Is there any other way?)
<ifreund>
no, I don't think so. I just wish passing the version directly into wl_registry_bind() was a bit less convenient :D
<snakedye>
Mine has its own set of issues and like most of my first clients is poorly written. This will be an opportunity to make it less worse ¯\_(ツ)_/¯
<novakane_>
ifreund: ah I see your border-color config is way cleaner than mine, I should have thought of that :P
<ifreund>
novakane_: you mean the labeled block based approach in render.zig?
<ifreund>
I've personally decided that if statements without curlies should never be split across multiple lines, and I intend to try and upstream that notion to zig fmt eventually
<novakane_>
ifreund: yeah, I get you, I don't like const on multiple line, I don't have the reflex for labeled block though
ino has joined #river
novakane_ has quit [Quit: WeeChat 3.2]
novakane has joined #river
<elshize>
hey, just updated river to master head, and my river module in waybar stopped working
<elshize>
Gdk-Message: 11:46:17.176: Error 88 (Socket operation on non-socket) dispatching to Wayland display.
<elshize>
Waybar v0.9.7
<elshize>
has anybody had a similar problem?
<ifreund>
elshize: yeah, that's my fault sorry, I screwed up forwards compatibility when I wrote the initial river module for waybar
<ifreund>
waybar master fixes that and also has support for urgent tags
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
<elshize>
I can't catch a break today, I don't think I'm destined to see my tags today :D
<ifreund>
well, you can also just revert that one river commit locally :P
<ino>
hi guys, I am having a very good time with river. :)
<ifreund>
anyhow, when you get it worked out you'll have a new urgent color to enjoy!
<ifreund>
off to boulder now, see y'all around o7
<ino>
in the repo it says breakages might happen because its on active development, but it has been very stable for me.
<elshize>
ifreund: yeah, too lazy right now, will do it later ;)
<elshize>
or rather just compile waybar from source
snakedye has quit [Ping timeout: 268 seconds]
<dnkl>
yambar now requires river-status-v2, and the river module has a new 'urgent' boolean tag
<dnkl>
novakane: big thanks for adding xdg-activation support!
<ino>
@dnkl yambar is great! I loved it. it supported alsa which I did not get from waybar, then I switched :)
<dnkl>
ino: really? Kind of weird not to support plain alsa imho...
<ino>
haha yes! it only supports pulse audio, that i never install because alsa mixer is enough for my needs :) I use a whole lot of apps of yours lol
<ino>
=D
<novakane>
dnkl: well thanks to you for making it easy to test it with foot, big help to implement it :P
<dnkl>
ino: I'm always happy to see someone else find my apps useful :)
<ino>
:] =D '=D
<dnkl>
Nulo: the yambar-alsa-PR has been merged to master. I'm fairly sure it'll fix your pulseaudio issue as well. But if not, let me know
<ino>
one day maybe pulseaudio too will be integrated to systemd (both created by lennart) then it will be renamed as "pulsed-sound-d" =D
ino has quit [Quit: Ping timeout (120 seconds)]
snakedye has joined #river
leon-p has quit [Quit: leaving]
<snakedye>
ifreund: what could trigger an urgent_tag? I'm trying to test it
<Misthios>
"pulsed-sound-d" plz no
leon-p has joined #river
<leon-p>
I think the river status protocol could have used a "done" event
<snakedye>
For when the urgency times out?
<leon-p>
nope, for grouping events
<snakedye>
it could be useful but I don't really see myself using it since I do the formatting after all events have already been dispatched.
Guest77 has joined #river
<Nulo>
I don't use tags in yambar because when using something in "all tags" it shows all 32 tags
<Guest77>
Hi is it possible to display 2 tags on one output side by side ?
<Nulo>
Guest77: Yes, use Mod+Ctrl+[num] with the default keybindings
Guest77 has quit [Quit: Client closed]
<leon-p>
river-tag-overlay now supports urgency
Guest706 has joined #river
keithhub has quit [*.net *.split]
st4ll1 has quit [*.net *.split]
keithhub has joined #river
st4ll1 has joined #river
<Guest706>
Nulo: i tried your sugestion, but, this obly pulls the windoes into the view, i would prefer tosplit my phisicl display into 2 seperate workspaces and be able to switch tags on each half of them
<Nulo>
Probably can be achieved with a specific feature of the software that organizes your windows
<Nulo>
the screen space can be freely divided into "monitors" which may or may not match the actual (multi-)monitor hardware configuration. If you have a monitor with a large resolution just divide it into two or more virtual monitors such that you can view two virtual desktops at a time.
<ifreund>
leon-p: yeah, river-status and river-control were the first two protocols I wrote, they're both pretty crappy
<ifreund>
I'm glad we spent so long iterating river-layout, it's far higher quality
<novakane>
leon-p: nice, I had a patch just to make it works but I see you add a great implementation to not have the popup everytime
<novakane>
I'm not sure `square-urgent-occupied-colour` is really useful, a urgent tags is obligatory occupied no? Just nitpicking
<Guest706>
Nulo: yes exactly like in herbstluftwm, i have not found a way to split the display under wayland
<Guest706>
Nulo: so, this is not achievable with river right ?
<Nulo>
Guest706: It is theorically achievable with a layout generator that does it, river is very flexible
<Nulo>
But none that I know of do that
Guest706 has quit [Quit: Client closed]
Guest706 has joined #river
<Guest706>
Nulo: Ok, thanks! i try to look into into layout
Guest93 has joined #river
snakedye49 has joined #river
snakedye has quit [Read error: Connection reset by peer]
Guest93 has quit [Client Quit]
snakedye has joined #river
<snakedye49>
I'm getting this error when I try to build river `./river/Server.zig:62:21: error: container '.wlroots' has no member called 'XdgActivationV1'`
<ifreund>
Guest706: river doesn't support that use-case well, at least not yet
Guest706 has quit [Quit: Client closed]
<snakedye49>
ifreund thanks
snakedye49 has quit [Client Quit]
<ifreund>
supporting it well requires a good chunk of addtional complexity, and I don't feel a need for that feature myself
<snakedye>
I don't even think it's possible currently considering you would have move windows across tags
<leon-p>
ifreund: well, there is still at least one thing missing from river-layout. But it's a minor issue, so I think we should just wait a few months to see if the protocol has other issues before possibly working on it again
<ifreund>
leon-p: Yeah, that was my thought as well, I kinda want to wait until we figure out how to expose the double-buffered nature of river's state to clients that care
<ifreund>
I want frame-perfect status bars
<leon-p>
btw, I sometimes have a crash when the graphics chip is over-stressed. But I can't tell it is just river or Linux entirely. In the second case it probably is an issue with libreboot
<ifreund>
hmm, yeah can't really help you there :/
<leon-p>
yeah, for now I just set the kernel trigger of the scrollock LED to "panic", so it lights up when Linux panics. When it happens again I know more
waleee has quit [Quit: WeeChat 3.2]
waleee has joined #river
ino has joined #river
novakane has quit [Quit: WeeChat 3.2]
<ino>
hi guys! just wanted to share a minor thing. when I run neofetch, it shows `sway` in the `WM` section instead of river. why is that? :)
<leon-p>
ino: because there is no proper way to actually know what compositor is running. neofetch just uses pgrep I think. Or it queries XDG_CURRENT_DESKTOP, which you may have set to "sway"
<ino>
leon-p thank you leon plickat! i had no idea why was that. -_- :] :]
elshize has quit [Remote host closed the connection]
elshize has joined #river
tdeo has joined #river
ext0l has joined #river
<Nulo>
Shouldn't bars be drawn above overflowed views?
<leon-p>
Nulo: that depends on the layer the bar is on. There are four layers: background, bottom, top and overlay.
<ifreund>
that is, the bar gets to choose
<ifreund>
and may or may not let you configure that
<Nulo>
yambar uses bottom
<Nulo>
Changing it to top works
<Nulo>
dnkl: Should this be changed or at least be made configurable?