<Pound_Hash>
So, `rivercarro` (layout generator) uses `exec rivercarro`, but the default init uses just `rivertile` (no exec)
<Pound_Hash>
After looking at the man page (and tldr) I don't understand what the difference is.
<NickH>
From a pratical perspective, if you use exec in your river init script, nothing after that line will be executed.
<NickH>
If you want to execute the lines after launching your layout generator you should run the layout generator in the background.
<NickH>
Eg "rivercaro &"
talismanick has quit [Ping timeout: 245 seconds]
<Pound_Hash>
Thanks for that
<Pound_Hash>
But then why doesn't the default config use either `exec` or `&`?
<Pound_Hash>
I guess that's because the `rivertile` command is the last one?
<Pound_Hash>
So the assumption is that we won't add additional commands after `rivertile` is run. If we want to run additional commands, we must run it in the background. And if we want to debar additional commands running, we use `exec`
Pound_Hash has quit [Quit: Pound_Hash]
tsraoien has quit [Ping timeout: 245 seconds]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
tsraoien has joined #river
tsraoien has quit [Ping timeout: 252 seconds]
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 276 seconds]
notzmv has quit [Ping timeout: 255 seconds]
talismanick has joined #river
talismanick is now known as Guest3945
Guest3945 has quit [Client Quit]
alismanickt has joined #river
snakedye has quit [Ping timeout: 245 seconds]
notzmv has joined #river
<NickH>
In the past the example config used exec but it confused some people.
<NickH>
The curret example init doesn't background rivertile because it is last comand in the script, so it doesn't need to.
Pound_Hash has joined #river
alismanickt has quit [Ping timeout: 240 seconds]
<Pound_Hash>
quitr
Pound_Hash has quit [Quit: Pound_Hash]
snakedye has joined #river
amy_ has joined #river
amy_ has quit [Client Quit]
amy_ has joined #river
amy_ has quit [Quit: WeeChat 3.4.1]
amy_ has joined #river
amy_ has quit [Client Quit]
mon_aaraj has quit [Ping timeout: 245 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 245 seconds]
mon_aaraj has joined #river
silv3r has quit [Ping timeout: 245 seconds]
mon_aaraj has quit [Ping timeout: 252 seconds]
silv3r has joined #river
mon_aaraj has joined #river
silv3r has quit [Ping timeout: 245 seconds]
silv3r has joined #river
waleee has joined #river
klim has joined #river
vipulogmx has quit [Ping timeout: 255 seconds]
adamcstephens has left #river [#river]
adamcstephens has joined #river
<tleydxdy[m]>
oh noo, I peaked into waybar's code
<tleydxdy[m]>
now I have to write my own, or get some other sane bar
snakedye has quit [Ping timeout: 252 seconds]
<leon-p>
tleydxdy[m]: we have a section on recommended software in the wiki
<tleydxdy[m]>
I remember trying those out, but only few supported river's tag thing iirc
<tleydxdy[m]>
even then I had to patch the river tag handling in waybar heavily, basically rewrote it
<tleydxdy[m]>
at the time I was like ye it's just the patch that was bad
<tleydxdy[m]>
err
<gbrlsnchs>
tleydxdy[m]: yambar supports river tags
<gbrlsnchs>
and it's written by the same dev from the foot terminal
<gbrlsnchs>
if you like foot you might like yambar as well
<tleydxdy[m]>
I'll try that out, thx
<tleydxdy[m]>
one of the thing is I have this sticky tag
<tleydxdy[m]>
and need the bar to not show occupancy for the tag and all that
<tleydxdy[m]>
ideally the bar should be provided by the layout generator, at least the tag portion
<tleydxdy[m]>
otherwise it's just endless patching
<leon-p>
the layout generator has nothing to do with the tags, so I don't think it would really help here.
<leon-p>
however since both bars and layout generators are just regular wayland clients, you can definitely write a program that does both
<tleydxdy[m]>
yes, but having it in river itself is not possible
<tleydxdy[m]>
because of how ifreund want to maintain it
Guest16 has joined #river
<tleydxdy[m]>
also you know stuff like showing the current layout and all that
<leon-p>
in river-tag-overlay I just assume that the main tags a user will use are the ones at the beginning of the bitfield and they can choose how many of them to display. All other will be ignored. Has worked well for me.
Guest16 has quit [Client Quit]
<leon-p>
we technically do have the concept of a layout name that could be showed in bars, however river-status doesn't offer that yet.
<tleydxdy[m]>
if by ignore you mean not set or clear that might work fine
<leon-p>
they are simply not displayed
<tleydxdy[m]>
one thing I ran into is when I click on the icons to set tags, it clears my sticky tag
tsraoien has joined #river
<n0r>
I'm still thinking about the float vs pseudo-float-because-no-layout thing. On what basis are windows ("properly") floated by default when I didn't use float-filter-add? Is there a way to prevent that?
<leon-p>
for example when they are not resizable
<n0r>
I have not had a not resizable yet...
<n0r>
Maybe I should just work on my behavior of cluttering some tags with a dozen windows and reduce/distribute them more. With only 2-3 visible windows, tiling would be usable on my small screen and toggling floating is available again. Main reason I don't use rivertile is 1366*720 is just too small to tile as many as I often have in visible status.
<n0r>
... visible state. Whatever.
<leon-p>
I wrote my layout so that by default only three windows are visible, works for me
<n0r>
So some windows have size 0?
<leon-p>
nope, they are simply behind other windows
<n0r>
Well... I guess at some point I should figure out how to get software from outside the distro repos...
vipulogmx has joined #river
mon_aaraj has quit [Ping timeout: 272 seconds]
mon_aaraj has joined #river
gbrlsnchs has quit [Read error: Connection reset by peer]
mon_aaraj has quit [Ping timeout: 245 seconds]
mon_aaraj has joined #river
talismanick has joined #river
notzmv has quit [Ping timeout: 240 seconds]
gbrlsnchs has joined #river
mon_aaraj has quit [Ping timeout: 252 seconds]
mon_aaraj has joined #river
Corentin has joined #river
Corentin has quit [Client Quit]
notzmv has joined #river
gwizon has joined #river
gbrlsnchs has quit [Quit: nyaa~]
snakedye has joined #river
<NikhilSingh[m]1>
i tried to read river tags got the gist but not completly to work with them (any resource where it has been documented a bit in depth)?
<leon-p>
tags are pretty simple, most explanations just aren't that great. Basically every window has a bit-field (like 100011, only with 32 0/1s) and every output has one too. If both a window and the output have at least one matching 1 in the same position, the window will be displayed, otherwise it remains hidden. And that's all.
<NikhilSingh[m]1>
thanks this much was the part that i got tried to understand sticky one code
<NikhilSingh[m]1>
got confused how that bit shift operation worked as echoing that was giving some result i didn't understand
<NikhilSingh[m]1>
ig guess it didn't worked everything is floating now.
<leon-p>
make sure stacktile is running
<NikhilSingh[m]1>
my mistake had to call stacktile after setting it from riverctl
<NikhilSingh[m]1>
worked. Thanks it is nice and suits my work flow
<leon-p>
glad you like it
<NikhilSingh[m]1>
leon-p Thanks mate the stack layout has made it so easy to configure the layout however i want ( i mean you just made it perfect )
<NikhilSingh[m]1>
River just adds the left|right focus and ig u had that pr too so thanks again.
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
<tleydxdy[m]>
shower thought, I think I found a way to make monocle mode work correctly for river
<tleydxdy[m]>
not sure if it'll get merged tho
<tleydxdy[m]>
basically, if the focused stacked view takes up all the usable area, then bring the view to the top of the stack
<tleydxdy[m]>
it should not affect anything else I think
<leon-p>
would require river to actually care about the dimensions of views, which right now it does not. The proper solution would be to just render in reverse focus order (although that also has some issues which were already discussed at length in IRC, should be in the logs somewhere). The end-goal though is to also make this controlled by clients, so it probably doesn't really make sense to invest time into this right now.
<NikhilSingh[m]1>
i was thinking with a approach of tags like if going in monocle mode then tagging a window to specific tag that is never gonna use for e.g 31 then if exiting monocle mode removing that tag from the window and mvoing back to the previous tag ( yet not able to figure out how to move back to the previous tag )
<tleydxdy[m]>
you mean render the stacked views in reverse focus order?
<leon-p>
tleydxdy[m]: all views are stacked. there is nothing preventing a layout generator from overlaying views.
<tleydxdy[m]>
but there's floated views right?
<leon-p>
yes
<tleydxdy[m]>
yeah, by stacked I just mean it's not floated
<leon-p>
ah I see
<leon-p>
views controlled by a layout generator are traditionally called tiled, although that might not always make sense
<NikhilSingh[m]1>
is this is the right way to do for stack tile as this not working for me.
<leon-p>
you need to also provide the name of the layout and need to quoate the entire command you want to send: riverctl send-layout-cmd stacktile "primary_ratio -0.05"
<NikhilSingh[m]1>
worked thanks
<tleydxdy[m]>
lol, oof my plan had a problem, it only works with two views
<tleydxdy[m]>
I need to cycle the focus stack instead
<tleydxdy[m]>
since it's doubly linked do I just change the first&last node?