<NickH>
I'm also waiting on the next release to get river/mode.
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
snakedye has joined #river
<plumeus>
This reminded me to double check my Waybar configs. I noticed I could add styling for "button.urgent" but how does one test that out?
<plumeus>
like, when is a tag urgent?
<ifreund>
plumeus: when activaction of a client is requested over the xdg-activation protocol
<ifreund>
you can test it by running e.g. `sleep 5 && tput bel` in foot then switching to another tag and waiting 5 seconds
Guest53 has joined #river
Guest53 has left #river [#river]
<plumeus>
Thanks, that worked.
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
mon_aaraj has quit [Ping timeout: 255 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 246 seconds]
mon_aaraj has joined #river
wrkzk has quit [Ping timeout: 276 seconds]
waleee has joined #river
snakedye_real has joined #river
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 246 seconds]
mon_aaraj has joined #river
simplefinger has joined #river
simplefinger has left #river [#river]
snakedye_real has quit [Quit: snakedye_real]
snakedye_real has joined #river
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
<mizzunet>
ifreund would you able expose API for current focused program's app-id. So, that yambar river module will be able to display it.
snakedye_real has quit [Ping timeout: 240 seconds]
<novakane>
the title is not enough for your use case?
<mizzunet>
title may be pretty long. Especially on browser.
<dnkl>
mizzunet: why not use the "foreign-toplevel" module (in yambar) instead?
<mizzunet>
Does that do the help? Let me try it
<mizzunet>
Great. It has app-id. Thanks (:
<novakane>
so I may remember it wrong but can't you set a max value for a string in yambar, iirc I did this for title
<dnkl>
novakane: s/can't/can
<dnkl>
;)
<novakane>
oops yeah :P
<ifreund>
my PineNote just arrived, now I just need to find time to figure out how to compile and flash a kernel to it with the proper patches :D
<ifreund>
then river will probably get better touch and tablet tool support
<novakane>
oh that was fast
<ifreund>
yeah, faster than I expected. I think their handling of shipping for the PineNote is a bit different than other products though. Only courier (DHL) shipping is available and they seem to ship from hong kong
<novakane>
that's cool, have fun :D
<novakane>
I'm curious to see how well it gonna works with river
<novakane>
we gonna need a video :P
<ifreund>
all in due time :)
<ifreund>
I think I may have to get into kernel dev and learn a lot more about KMS/DRM to get things working how I want, but that's not a bad thing really
Franciman has left #river [WeeChat 3.5]
<novakane>
can't hurt to learn more about this when you contribute to wlroots
<mizzunet>
novakane I'm fine with app-id. Glad to know.
fitrh has joined #river
<leon-p>
I wonder how good the display and digitizer of the pinenote are compared to the product(s) it copies.
<ifreund>
the factory android install works quite well, I don't have any other E-Ink devices to compare it to however
fitrh has quit [Remote host closed the connection]
<plumeus>
Oh yeah, been meaning to ask about River's cursor hiding.
<plumeus>
I'm not on the latest commit but the cursor doesn't unhide itself unless I move my cursor over some window. Is this intended?
<plumeus>
Example: go to an empty tag and let the cursor hide. Moving it won't unhide it until the cursor goes over some window or waybar.
<ifreund>
plumeus: can't reproduce...
<plumeus>
This is a bit annoying when my cursor is at the very edge of the screen with the default padding
<plumeus>
oh, okay, then let me update to the latest commit
<ifreund>
could potentially have something to do with your cursor theme as well, not sure
<plumeus>
I am on NixOS, for one. Lemme check about my theme
<plumeus>
Something to note: can't reproduce this on a nested River instance, probably because the entire thing gets treated as a window. okay, going to try latest commit
<tiosgz>
iirc i had something similar (but prolly not same) happen with swaybg, coz it doesn't set cursor. not sure how i'd go about consistently reproducing it
<ifreund>
ah, yeah if you're using swaybg this is probably a swaybg bug
<leon-p>
yeah, client not setting the cursor is my guess as well. client but
<leon-p>
s/but/bug/
<plumeus>
I've not made any changes to my background
<plumeus>
I used the default init aside from input configs and keybinds, and stuff like gammastep or swaylock.
<leon-p>
also I am pretty sure swaybg sets its input region, so it not setting a cursor is fine
<tiosgz>
oh wait, i can reproduce it right now with just river's background (no wallpaper)
<plumeus>
Just reproduced on my nixos setup with latest commit
<plumeus>
Is not setting a wallpaper unusual?
<ifreund>
I don't set my wallpaper either...
<tiosgz>
i've seen more people set it than not so far, but prolly depends
<tiosgz>
the river community is more wallpaper-less
<plumeus>
okay, then... let me check where my cursor theme is coming from
<ifreund>
I have 'riverctl xcursor-theme Adwaita' in my init
<plumeus>
it was the thing that was screwing with my attempt to try implementing that feature when I wanted to contribute
<plumeus>
yep, that fixed it for me
<leon-p>
I know from experience that even with a theme missing pretty much all cursors, it should still render something. Pretty sure the x library included by libwayland-cursor just defaults to a default cursor
<plumeus>
Also, the cursor behaves really weirdly on alacritty. No issues on foot. idk what's up with alacritty.
<tiosgz>
hmm, i thought river would pick XCURSOR_THEME ?
<tiosgz>
(also fixed with riverctl xcursor-theme)
<plumeus>
my `XCURSOR_THEME` isn't set
<ifreund>
tiosgz: hmm, we currently only use XCURSOR_THEME to set Xwayland cursors
<plumeus>
also, I thought it didn't read that env without enabling `-DXWayland` or something? I forgot what it was
<plumeus>
yeah
<ifreund>
I don't really have a strong opinion there or remember why it was done that way
<plumeus>
But I do have `-DXWayland` set
<ifreund>
though I do prefer configuration through riverctl rather than environment variables in general
<ifreund>
what was weird about alacritty exactly? I don't notice anything different really
<plumeus>
I get different behavior from not setting any cursor or doing `riverctl xcursor-theme <non-existent-theme-name>`
<plumeus>
On Alacritty, the cursor never updates for me. Once it becomes hidden, it remains that way. Also, if I was on a tag with a program that changed my cursor theme and I switch to alacritty, it stays as that theme (until it goes hidden)
<ifreund>
can't reproduce either of those, what alacritty version?
<ifreund>
I seem to have 0.10.1
<plumeus>
0.10.1 too
<plumeus>
also worth noting is that my cursor becomes ridiculously small in mpv.
<plumeus>
I wonder if the fact that I do `wlr-randr --output eDP-1 --scale 1.5` is relevant... idk
<tiosgz>
you can try XCURSOR_THEME and/or XCURSOR_SIZE (:
<plumeus>
Both are only read when enabling XWayland, iirc. Not that it matters.
<ifreund>
can't reproduce small cursor in mpv either...
snakedye has quit [Ping timeout: 240 seconds]
<plumeus>
weird, idk why my setup is such a mess then
snakedye has joined #river
<plumeus>
ifreund, do you use XWayland? Maybe I should disable it to see if it changes any behavior
<ifreund>
Yes, though I don't actually run X11 programs very often
<plumeus>
welp, I'm out of ideas
<plumeus>
`mpv` definitely seems to be setting a custom cursor for me
<plumeus>
they have their built-in unclutter, even
<ifreund>
indeed they do
<plumeus>
maybe I could try setting the `wlr-randr` scaling to 1 and see if that changes anything
<plumeus>
yeah, even then, the cursor seems smaller on `mpv`, if only by a bit.
<plumeus>
So it just seems to be that the cursor theme isn't scaling whatsoever.
<plumeus>
wait... my cursor is working fine on Alacritty now... what?
<plumeus>
just restarted River and it's not working again...
<plumeus>
I have no idea
<plumeus>
maybe I was hallucinating...
<plumeus>
wait... now my cursor size on `mpv` is fixed... ???
<plumeus>
Restarted River again and it fixed Alacritty too, now...
<plumeus>
Possible explanation: Maybe I needed to start a new instance of Alacritty/MPV after I set a cursor theme. So everything fixed itself when I put it in my init config.
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
<ifreund>
hmm, this is really stupid. It seems the only real way for pure-wayland clients to coordinate on using the same cursor theme is currently for them to read XCURSOR_THEME/XCURSOR_SIZE
<ifreund>
ignoring client cursors isn't a solution, it's useful for clients to be able to set a hand cursor when hovering a button or a vertical bar cursor when hovering text
<plumeus>
Yeah, did a bit of testing. `riverctl xcursor-theme` definitely seems effective even without `-DXWayland`. I don't really see why we shouldn't be reading those env vars if that's the case.
<tleydxdy[m]>
then what do you mean by server side
<leon-p>
does any server implement the cursor-shapes eextension? Is there an "official" PR for it to get merged upstream into wayland-protos?
mon_aaraj has quit [Ping timeout: 240 seconds]
<tleydxdy[m]>
the server has a list of cursors the client can choose from?
<ifreund>
plumeus: river doesn't read any cursor related environment variables except XCURSOR_PATH, it sets XCURSOR_THEME/SIZE only when built with Xwayland support currently
<ifreund>
riverctl xcursor-theme will be effective for setting the cursor used by the server when no client has pointer focus
<ifreund>
but if built without Xwayland support it won't communicate that theme/size to clients in any way
<ifreund>
leon-p: I assume whatever the chrome-os compositor is called does
mon_aaraj has joined #river
<ifreund>
and no it hasn't been proposed to wayland protocols, I'd love to see someone take on that task
<plumeus>
But we do want it to communicate, right?
<leon-p>
tleydxdy[m]: obviously a client still needs control over cursor shape and client side cursors need to be an option for clients that require super specialized cursors, like GIMP. Server side cursors simply means the server has a catalog of default cursors a client could choose from
<ifreund>
plumeus: yes, the problem is that the current wayland protocol doesn't provide any way to do so
<tleydxdy[m]>
I see yeah, that makes sense
<tleydxdy[m]>
isn't that kinda how every other platform worked?
<ifreund>
I think I'll change river to set XCURSOR_THEME/SIZE even when built without xwayland support
<ifreund>
pretty sure that's what sway and others do
<ifreund>
oh, we totally do set XCURSOR_THEME/SIZE even if not built with xwayland support, I just can't read
<plumeus>
huh...
<ifreund>
river's not doing anything wrong here given the current sorry state of affairs as far as I can tell
<plumeus>
Good to know.
<ifreund>
I'm personally convinced that a protocol in the style of that cursor-shapes chromium protocol is the way to go, don't have any time to dedicate to that in the forseeable future though
wrkzk has joined #river
waleee has quit [Ping timeout: 276 seconds]
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
<plumeus>
I was talking to another guy who started using River recently and that reminded me
mon_aaraj has quit [Ping timeout: 240 seconds]
<plumeus>
is there a way to make a keybinding that works while you're holding the key?
<plumeus>
like, for example, make it so you can adjust the brightness of the screen while holding the brightness buttons, as opposed to having to hit and release the key 10 times
<leon-p>
there are repeat binds
mon_aaraj has joined #river
<plumeus>
ah, found it
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 264 seconds]
mon_aaraj has joined #river
cabal704 has joined #river
<nor[m]1>
I'm back in floating mode without layout generator. Automatic tiling is just not for me :D Rivers floating behavior is actually really nice once I got used to it though. Back when I started using river we discussed how views stacked in a seemingly odd order in floating. But now I actually prefer the current behavior. It's basically "focused on top, the rest ordered manually, not automatically".
cabal704 has quit [Quit: WeeChat 3.5]
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
gwizon has quit [Ping timeout: 240 seconds]
mon_aaraj has quit [Ping timeout: 276 seconds]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
dbuckley has quit [Read error: Connection reset by peer]
dbuckley has joined #river
cabal704 has joined #river
cabal704 has quit [Client Quit]
waleee has joined #river
snakedye has quit [Ping timeout: 246 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
jaafarrc has joined #river
<jaafarrc>
How do I autostart PipeWire properly alongside river? (I'm using a non-systemd distro, for the record.)
<Shinyzenith[m]>
just run pipewire, pipewire-pulse and wireplumber manually in your setup script
<Shinyzenith[m]>
I append a setsid -f just to be safe
<jaafarrc>
That's exactly what I tried but it doesn't work
<jaafarrc>
I'll retry and I'll show you what I mean
<Shinyzenith[m]>
Do you have any blocking processes before it?
<tleydxdy[m]>
just add it to your usual supervision tree?
<jaafarrc>
Shinyzenith[m]: Don't know what those are, so probably a no.
<tleydxdy[m]>
since most likely you want it auto restarted if it crashes
<Shinyzenith[m]>
tleydxdy[m]: I'm on runit and afaik there's no service file for runit for me on artix so this is pretty much the only solution I have
<tleydxdy[m]>
write one ig
<Shinyzenith[m]>
Smallcreek: might wanna pastebin your config file so someone can take a look
<jaafarrc>
Shinyzenith[m]: Of course, I'll just triple-check something and show you the config after that.
<Shinyzenith[m]>
Alright
mon_aaraj has quit [Ping timeout: 276 seconds]
<jaafarrc>
I use this script: `https://termbin.com/zwhn`, and when I'm on river, I run `pulsemixer` to test the audio: I expect to see " Built-in Audio Analog Stereo" or something along the lines of that, but instead I get "Dummy Output," and no audio plays.
mon_aaraj has joined #river
<jaafarrc>
s///
<jaafarrc>
The bottom of the Termbin is the interesting part.
duncaen has quit [Read error: Connection reset by peer]
duncaen has joined #river
snakedye has quit [Ping timeout: 272 seconds]
snakedye has joined #river
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
cabal704 has joined #river
<leon-p>
jaafarrc: I think that's just one recent version of either pulse audio or alsa-drivers being messed up. Have the same bug right now. Try restarting pulseaudio until it finds the correct device
<jaafarrc>
leon-p: Pulseaudio? But I have Pipewire.
<leon-p>
(don't restart too often and too aggressively though, that will mess with rtkit-daemon which can easielly nuke your session)
<leon-p>
well, then it's alsa related
<leon-p>
same thing really
<jaafarrc>
So... restarting ALSA? I don't quite understand.
<leon-p>
you can't really restart alsa, it's a kernel thing. But try restarting your audio server, which in your case would be pipewire
<jaafarrc>
Of course I didn't think that, I was just trying to understand what you meant. I'll try that Pipewire restart solution later and tell you what happens.
<leon-p>
what I think is happening here is that some recent alsa update messed with some drivers or something