ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/ifreund/river || channel logs: https://libera.irclog.whitequark.org/river/
waleee has quit [Ping timeout: 276 seconds]
leon-p has quit [Quit: leaving]
snakedye has quit [Ping timeout: 272 seconds]
leon-p has joined #river
novakane has joined #river
snakedye has joined #river
<dnkl> ifreund: re. performance on the pinebook; I don't notice any difference between river and Sway
<dnkl> but then the pbp isn't exactly a speed daemon anyway
<dnkl> surfing is "barely" doable
<dnkl> coding is fine, as long as you don't spend too much time compiling (i.e. I wouldn't do rust on the pbp. Not that I'd do rust anyway, but still)
<dnkl> I think for general desktop usage, the GPU is good enough - it's the CPU that's bottlenecking it
<ifreund> dnkl: interesting, thanks for letting me know. I guess damage tracking doesn't really make much difference for browser performance
<ifreund> I'd think that sway might get slightly better battery life though until I finish up river's damage tracking implementation
<dnkl> could be. Haven't done much "idling" on it. I'm either in firefox, which automatically eats battery (on river and Sway alike), or compiling/installing things
<dnkl> battery life is still pretty good though
<ifreund> nice :)
<leon-p> "the GPU is good enough - it's the CPU that's bottlenecking it" So it's the inverse of my X200 :P
<leon-p> The pentium is still fine for most of what I do, but hardware accelerated video playback just does not work with modern formats
snakedye has quit [Ping timeout: 265 seconds]
snakedye has joined #river
<dnkl> novakane: are you still using yambar on river? Is your conf available somewhere? I'm interresting in seeing if you have any river settings I can use...
snakedye has quit [Ping timeout: 256 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
snakedye has quit [Read error: Connection reset by peer]
<novakane> dnkl: not right now, though my configs are still here https://git.sr.ht/~novakane/dotfiles/tree/main/item/config/yambar
<ifreund> dnkl: here's a screenshot of my current waybar setup if you're looking for inspiration: https://0x0.st/-Wdf.png
<ifreund> tags that have views but aren't focused have just the outline, focused tags without views have just the inner part filled in, focused tags with views have the full rectangle filled
<ifreund> on my laptop I use leon-p's river-tag-overlay instead of a bar to save space: https://git.sr.ht/~leon_plickat/river-tag-overlay
<dnkl> ifreund: thanks! that's sort of what I have too, except I hide unfocused tags without views
<dnkl> novakane: thanks!
antaxiom has joined #river
<antaxiom> Hello
<ifreund> o7
<antaxiom> I just wanted to thank you and the other devs
<antaxiom> For your great work on river, I've enjoyed it a lot
antaxiom has quit [Client Quit]
antaxiom has joined #river
<antaxiom> Hi
<ifreund> that's nice to hear, glad river is working well for you :)
<antaxiom> I think I left on accident, IRC is confusing
<antaxiom> Yep!
<antaxiom> Well that's it, I hope you have a nice day (or night)
antaxiom has quit [Remote host closed the connection]
waleee has joined #river
<novakane> damn I'm gonna give up on smart borders, it's a shitshow of if else condition, I'm going crazy lol
<novakane> re adding borders doesn't want to works :/
noopdecoder has joined #river
noopdecoder has quit [Client Quit]
noopdecoder has joined #river
<leon-p> novakane: you might have more luck if you implement it as a stand-alone client instead of integrating it into your layout
noopdecoder has quit [Client Quit]
<novakane> leon-p: hmm that's not a bad idea, I could try, I don't how it would be integrated with layout client though
<novakane> or I just wait for river-control-v2 :P
<novakane> it would be cool a client that add smart border and gaps to all layout client
<dnkl> on scale 1..10, how ugly is having "renice -n -10 $PPID" in river's init?
<leon-p> novakane: considering that changing the border size is already a bit hacky, you can just send your layout generator a user command to turn off the gaps
<dnkl> dnkl: pretty ugly when you realize all conf processes inherits the niceness
<ifreund> dnkl: heh, what was your goal? Faster execution of the init script on startup?
<dnkl> ifreund: nah, for river itself (PPID, not PID)
<dnkl> works, but need to change all spawn commands to use "nice"
<ifreund> dnkl: really? I thought the setsid() after forking for the spawn commands would avoid niceness being inherited
<ifreund> wouldn't starting river with nice -n -10 river work?
<dnkl> ifreund: will try that next. the idea was to automate it though. of course, I can just as well write a wrapper script for river...
<dnkl> this was a last minute experiment before I had to run. might have gotten some details wrong
<ifreund> I think most people will want to start river with a wrapper script to set environment variables and whatnot
<ifreund> for example XDG_SESSION_TYPE=wayland XDG_CURRENT_DESKTOP=river to make xdg-desktop-portal work for screensharing
<ifreund> I could be wrong though and setsid() doesn't reset the nice value
<ifreund> sched(7) is the man page about this, but it doesn't really answer that question afaict
<dnkl> ifreund: sched(7) says "Child processes inherit the scheduling policy and parameters across a fork(2). The scheduling policy and parameters are preserved across execve(2)."
<dnkl> ifreund: it also mentions a reset-on-fork flag that can be set, but doesn't appear to be set by default
<dnkl> fwiw foot also calls setsid() and niceness "leaks" through to the terminal's client applications, similar to river's spawn
<ifreund> dnkl: ah, I missed that reset-on-fork flag, thanks
<ifreund> Not sure if it would make sense for river to set that or not tbh
<dnkl> ifreund: gut feeling is don't set it. Except that I can't get "spawn 'nice -n 0 ...' to work...
<ifreund> without knowing exactly what you tried, I blame shell quoting
<dnkl> ifreund: riverctl map normal $mod+Shift Return spawn 'nice -n 0 footclient'
<dnkl> footclient starts, but with -10 niceness
<dnkl> anyways, this was just an experiment. I haven't had any performance issues with river whatsoever :)
<ifreund> huh, interesting
<ifreund> glad river's been snappy enough though
<ifreund> dnkl: RE: xdg-activation, I plan on fixing the last 2 open bug reports and then tagging 0.1.0 as my top priority, I definitely plan to implement that soonish though
<dnkl> no worries, and no rush :) couldn't remember if you had mentioned it or not, and couldn't find anything on the issue tracker
<dnkl> ooooh, hold on... nice(1) says "add integer N to the niceness (default 10)"
<dnkl> -10 + 0 = -10
<ifreund> no, I don't think there was anything, good to have something to track it
<ifreund> heh, talk about intuitive defaults
<dnkl> heh, sure thing... "spawn 'nice -n 10 ...'" gives me a niceness of 0
notzmv has quit [Ping timeout: 256 seconds]
snakedye has joined #river
dbuckley has quit [Ping timeout: 252 seconds]
dbuckley has joined #river
dbuckley has quit [Ping timeout: 240 seconds]
dbuckley has joined #river
novakane has quit [Quit: WeeChat 3.2]
notzmv has joined #river
dbuckley has quit [Ping timeout: 240 seconds]
dbuckley has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river