kennylevinsen has quit [Remote host closed the connection]
coder_kalyan has quit [Remote host closed the connection]
anjan has quit [Remote host closed the connection]
anjan has joined #river
coder_kalyan has joined #river
kennylevinsen has joined #river
pkap has joined #river
novakane has quit [Quit: WeeChat 3.3]
novakane has joined #river
novakane has quit [Quit: WeeChat 3.3]
novakane_ has joined #river
novakane has joined #river
coder_kalyan has quit [Remote host closed the connection]
novakane has quit [Remote host closed the connection]
anjan has quit [Remote host closed the connection]
kennylevinsen has quit [Remote host closed the connection]
anjan has joined #river
novakane has joined #river
coder_kalyan has joined #river
kennylevinsen has joined #river
tatti has joined #river
<tatti>
hello everyone, I was trying to set wallpaper using imv but it covers the whole screen with "imv -f -t 5 ~/Pictures/wallpapers &" anyone know how to fix this?
<tatti>
I used to use feh on qtile, but feh doesnt work on river whilst imv should, but I seem to be clueless with imv
<leon-p>
tatti: swaybg is a decent wallpaper program for Wayland
<leon-p>
feh has not Waylandsupport to my knowledge and I never heard of imv being able to set a wallpaper
<tatti>
Yeah I was looking for something that works both on wayland and X
<tatti>
I suppose i stick with feh for X and swaybg for river
<tatti>
thanks anyway
tatti has quit [Quit: Client closed]
ext0l_ has quit [Ping timeout: 265 seconds]
novakane_ has quit [Quit: WeeChat 3.3]
andrea has joined #river
snakedye has quit [Ping timeout: 265 seconds]
snakedye has joined #river
waleee has joined #river
novakane has quit [Remote host closed the connection]
novakane has joined #river
waleee has quit [Ping timeout: 264 seconds]
waleee has joined #river
snakedye has quit [Ping timeout: 264 seconds]
waleee has quit [Ping timeout: 268 seconds]
waleee has joined #river
yyp has quit [Read error: Connection reset by peer]
yyp has joined #river
waleee has quit [Ping timeout: 268 seconds]
waleee has joined #river
leon-p has quit [Quit: leon-p]
snakedye has joined #river
priner has quit [Ping timeout: 265 seconds]
entenel has quit [Ping timeout: 265 seconds]
Ollie[m] has quit [Ping timeout: 265 seconds]
priner has joined #river
entenel has joined #river
Ollie[m] has joined #river
pkap has quit [Quit: Client closed]
snakedye has quit [Ping timeout: 252 seconds]
waleee has quit [*.net *.split]
novakane has quit [*.net *.split]
andrea has quit [*.net *.split]
coder_kalyan has quit [*.net *.split]
kennylevinsen has quit [*.net *.split]
anjan has quit [*.net *.split]
travankor has quit [*.net *.split]
ecocode__ has quit [*.net *.split]
zxtx has quit [*.net *.split]
qyliss has quit [*.net *.split]
inclement has quit [*.net *.split]
zdykstra has quit [*.net *.split]
notzmv has quit [*.net *.split]
emersion has quit [*.net *.split]
chipps has quit [*.net *.split]
Phyrric has quit [*.net *.split]
hspak has quit [*.net *.split]
omni has quit [*.net *.split]
anb1 has quit [*.net *.split]
buffet has quit [*.net *.split]
ifreund has quit [*.net *.split]
novakane has joined #river
travankor has joined #river
waleee has joined #river
kennylevinsen has joined #river
notzmv has joined #river
Phyrric has joined #river
emersion has joined #river
chipps has joined #river
hspak has joined #river
ecocode__ has joined #river
zdykstra has joined #river
andrea has joined #river
coder_kalyan has joined #river
anjan has joined #river
anb1 has joined #river
omni has joined #river
inclement has joined #river
buffet has joined #river
qyliss has joined #river
zxtx has joined #river
ifreund has joined #river
sogun has joined #river
<sogun>
Hello, I am curious, why riverctl doesn't have get-focused-tags and get-view-tags. Actually it has not get- commands at all. Does anyone know?
<sogun>
(I wanted to implement simple switch to next tag keybind with something like riverctl set-focused-tags $(( $(riverctl get-focused-tags) << 1)), but it looks like i have no luck...
<ifreund>
sogun: mainly because riverctl being a CLI program causes stuff like that to be inherently racy and a better interface is needed
<sogun>
i tried to, but it ignores me closing pipe and keeps running. But I found this one https://gitlab.com/SillyPill/river-shifttags . Which does exactly what I needed. Thank you, for response and nice work
chipps has quit [Quit: WeeChat 3.3]
snakedye has joined #river
<sogun>
By the way is there any hope to see (or help with) progress on issue 357? I am coming from Herbstluftwm so I feel completely lost without it...
leon-p has joined #river
<leon-p>
sogun: it's more likely that the focus will be on a window management protocol, at which point river no longer needs to know anything about tags
snakedye has quit [Ping timeout: 264 seconds]
<sogun>
so river will become more close to Xorg + WM arragment...
<ifreund>
sogun: this use case will be supported eventually because I want to use multi monitors that way, it may take a while though
<leon-p>
WM+display server, but not like Xorg
<ifreund>
yeah, very far away from Xorg
<sogun>
I meant from high level perspective. And arragment only. There is display server and a client which actually drives window placement etc...
<leon-p>
from a high-level perspective, on X a WM overrides window placement, while on river it will just suggest it
<sogun>
Does it matter for regular user? (sorry if it looks like ignorance, but I am curious)
<leon-p>
kinda, maybe. X allows you to have multiple clients forcing their opinion onto the window placement, which will result in things fighting and getting weird and funky. On river that is a situation that simply should not be allowed.
<sogun>
I see, it is technically possible that any X client starts to arrange other clients.
snakedye has joined #river
<leon-p>
also if a WM does something really stupif, river could theoretically intervene, which might be worth investigating
<sogun>
But what would prevent in River client to speak the management protocol and try to arrange others as well?
<leon-p>
sogun: simple: have a WM interface and only allow a single client to bind it
<sogun>
So the one coming first will just grab the privilege?
<leon-p>
that's probably how it will be done at first yes. Maybe we can investigate a way to only allow authorized clients to bind it, but Wayland client authorisation isn't exactly where it should be rn
snakedye has quit [Read error: Connection reset by peer]
<sogun>
Yeah I noticed... People talk about its security, but anything can just record screen, set up outputs or whatever protocols are implemented.
snakedye has joined #river
<leon-p>
to be fair, a server can deny any client anything, the problem is really just authorisation. and that is really more of a UNIX problem. Turns out UNIX and POSIX are kinda shitty, who would have guessed
<sogun>
Well, if linux is only concern, then i could imagine something like compositor starting privileged client in mount namespace with privileged socket.
<leon-p>
Wayland is not linux specific. It runs on FreeBSD as well. Not sure if there is something portable that allows process authentication
<sogun>
I don't know about anything rootless. You could have suid helper of course, then create bsd socket, chown it to some user and start privileged client as that user. But i guess something on protocol level would be more systematic.