rodrgz_ has quit [Remote host closed the connection]
leopoldek has quit [Ping timeout: 240 seconds]
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 240 seconds]
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 245 seconds]
Guest52 has joined #river
Guest52 has quit [Client Quit]
robertss has joined #river
<robertss>
I'm a few weeks into using river. I've played around with the configs for river and waybar and nearly have it behaving just like my xmonad configuration. Just a few more tweaks and I might never go back.
<leon-p>
nice!
<robertss>
Best surprise for me was the foot terminal. I like it better than the urxvt that I was using.
<leon-p>
I totally missed how river grew popular, surprised me a bit to suddenly see it pop up in so many spaces
<leon-p>
yeah, foot is great
<robertss>
I'd looked briefly at sway and vivarium. I was curious about Hyprland but I couldn't compile it on my Void laptop. River seems to be fitting my needs.
waleee has quit [Ping timeout: 240 seconds]
robertss has left #river [Leaving]
taupiqueur3 has joined #river
srobert has joined #river
srobert has left #river [#river]
taupiqueur3 has quit [Ping timeout: 240 seconds]
jao has quit [Ping timeout: 252 seconds]
elshize has joined #river
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 240 seconds]
midgard has quit [Server closed connection]
midgard has joined #river
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 240 seconds]
taupiqueur3 has joined #river
elshize has quit [Ping timeout: 240 seconds]
ayushnix has joined #river
elshize1 has quit [Ping timeout: 240 seconds]
ayushnix has quit [Changing host]
ayushnix has joined #river
taupiqueur3 has quit [Ping timeout: 245 seconds]
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 245 seconds]
hryx has quit [Server closed connection]
hryx has joined #river
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 246 seconds]
taupiqueur3 has joined #river
TheAnachron has joined #river
taupiqueur3 has quit [Ping timeout: 245 seconds]
taupiqueur3 has joined #river
taupiqueur3 has quit [Ping timeout: 246 seconds]
ayushnix has quit [Remote host closed the connection]
kraem has quit [Remote host closed the connection]
kraem has joined #river
kraem has quit [Remote host closed the connection]
kraem has joined #river
elshize has joined #river
elshize has quit [Client Quit]
elshize1 has joined #river
leopoldek has joined #river
JustineSmithies has joined #river
<JustineSmithies>
I've a question about tags and dual screens. I get that an output can have 32 tags but most folk use 9 and you can then have the rest as scratchpads for example. But if I connect another screen do both screens then get 32 tags each or is that dived by the number of outputs ( screens ) ?
<RZ_MJ[m]>
Both get 32 Tags. Tags are orthogonal to outputs. Changing the tags of a view (aka window) doesn't change the output it is on. Moving a view to a different output doesn't change the tags it has.
<JustineSmithies>
Ok thanks for that explanation. It'll take a minute to get my head around tags as
<JustineSmithies>
i've always been used to workspaces on Qtile or Sway
<ifreund>
Having a shared set of tags across all outputs would make some things nicer but would also cause issues with windows being assigned to multiple tags at once
<ifreund>
having a wayland client rendering on two outputs at the same time is possible, but the window would have to be the same size on both
<ifreund>
which kinda breaks tiling
<RZ_MJ[m]>
I like the way it is. To me outputs and tags (or workspaces) are fundamentally distinct things and I never liked how sway and others have an implicit interaction between the concepts.
<JustineSmithies>
Hey sorry if I've been misunderstood ? I'm not complaining or wanting changes, I am just trying to work out in my head how this will work for me know and what advantages tags could have for me on my dual screen setup.
<JustineSmithies>
At present I'm dailying Sway on my main and expereimenting with River on a test laptop until I feel I'm comfortable enough to jump ship. I am really liking the features of River and hope I can make it my new DM.
<ifreund>
oh no worries, I'm the one who wants to try out shared tags across outputs at some point xD
<ifreund>
I don't really use the feature of assigning multiple tags to a window, I just leave windows on the tags I expect them to be on and focus multiple tags at once
<JustineSmithies>
My wishlist so far would be to see rules for matching app_id or titles and carrying out an action say to move to a tag and or output. Also a riverctl spawn blahblah -tag 2 -output HDMI-1-A for example
<JustineSmithies>
Also a hooks kind of system whereby you could say on a new window opening spawn a script and the same for on window close . I'm sure there could be plenty more too ;)
<JustineSmithies>
Anyway I'm running before I can walk so I'll shut up for now.
<RZ_MJ[m]>
"Advantages for dual screen" are probably a personal taste thing. I'd argue rivers system has 2 advantages: First there are n tags per output instead of just n in total (n being the amount of tags you have keymappings for). More is always better, right? ;) And second moving between outputs and moving between tags are separate things. In sway I'd double check "Wait, what output did I move this to implicitly by moving it to workspace 7?" But
<RZ_MJ[m]>
people used to sway/qtile/... could probably explain why their approach has advantages from their pov.
<JustineSmithies>
Good point RZ_MJ[m]
<JustineSmithies>
Is there a way in river to query the xkb current layout? In sway I could swaymsg -t get_inputs | jq '.[0].xkb_active_layout_name'
<ifreund>
nope, not yet
<JustineSmithies>
np
<JustineSmithies>
Is there another release out soon? Only reason I ask is that I see there has been a lot of progress since Feb 10th. I'm using void but I'm capabale of make a river-dev template that pulls the latest commit instead of the current release.
<JustineSmithies>
Just so I can explore the latest ;)
<ifreund>
JustineSmithies: The best estimate I can give for 0.3.0 is sometime in August
<ifreund>
there's certainly been a lot of progress on master branch but it also has a lot more bugs than 0.2.4 currently so be warned if you do choose to check it out :)