tsujp has quit [Remote host closed the connection]
snakedye has quit [Ping timeout: 255 seconds]
notzmv has quit [Remote host closed the connection]
noopdecoder has joined #river
noopdecoder has quit [Client Quit]
notzmv has joined #river
<ifreund>
just merged the breaking river-layout-v3 and riverctl spawn changes, y'all may want to update your configs
<novakane>
nice!
ecocode_ has joined #river
novakane has quit [Quit: WeeChat 3.2]
novakane has joined #river
<novakane>
I was wondering why my layout client wasn't working, I update river but forgot to build it smh
<ifreund>
heh
waleee has joined #river
<novakane>
anyway rivercarro is updated to river-layout-v3
<ifreund>
nice!
<ifreund>
did you get the smart borders thing working by the way?
<novakane>
not fully, I kinda put this on hold with river-layout-v3 comming, but tbh I think right now the implementation would be a bit too hacky, not sure to like it
leon-p has joined #river
<leon-p>
let's see how many "bug reports" there'll be about spawn and layouts no longer working :P
<novakane>
yeah... a lot :P
<novakane>
Didn't about it before restarting river but now the spawn command don't like bash array with `arr[@]`
<novakane>
need to use `arr[*]
<novakane>
thought*
<leon-p>
for me it actually fixes a bug: I use a gsettings command to turn of window buttons on GTK header bars. That did not work previously, because I need to set it to "" (empty string), which would get lost in translation. Now it works fine.
<novakane>
wow fixing a gtk bug that's crazy :P
<elshize>
so I was wondering; rivertile, and most other layout generators, doesn't support layout per tag. to me, layout per tag seems natural. and I was wondering how yall fell about that. is that something you'd want or something you don't need?
<elshize>
my reason for using it is not even layout per tag, but say the width of the window, on some tag I might want to increase a size of the main window but not on others. things like that, something that requires tweaking the default for a while on one tag.
<novakane>
I mean kile and stacktile have per tags layout so that's like half of layout generators
<leon-p>
elshize: it's probably based on how you see tags. If you see tags like you'd see sway workspaces, as completely separate environments, then of course you expect different layouts per tag. But that is not what tags are, river does not have workspaces / multiple desktops. Tags are basically just groups of windows. You do not switch between tags, you activate and deactivate them individually. Think of it more
<leon-p>
like automatically minimizing and restoring windows belonging together rather than switching to a different virtual desktop.
<elshize>
novakane: didn't realize stacktile supported that
<leon-p>
elshize: I added it to stacktile a few days ago. I don't nevessarily need it, so I might remove it later, but for now I am trying it out.
<elshize>
leon-p: that's an interesting point
<leon-p>
note that it breaks if you activate multiple tags, as is expected.
<leon-p>
anyway, stacktile does what you want and has recently been updated to river-layout-v3. It even supports replicating rivertiles behaviour if you prefer that
<elshize>
leon-p: so say in your setup, do you activate and deactivate with separate keybindings?
<leon-p>
elshize: I use the same keybinds for tags as the example config.
<elshize>
ok, let me check, I don't remember what example config was :)
<elshize>
I'm using kile atm, so I do have layouts per tag, but I was just wondering if i'm missing some good workflows
<leon-p>
Super+{1..9} to activate only a specifc tag, Super+Ctrl+{1..9} to toggle a tag. Super+Shift+{1..9} to set a windows tag to only a specific tag and Super+Ctrl+Shift+{1..9} to toggle a windows tag
<elshize>
trying to understand is all
<elshize>
ok, I seem to have the same but just never used the super+ctrl ones
<elshize>
I see what you're saying now
<elshize>
I'll experiment with it, thanks for clarifying!
<leon-p>
elshize: to come back to your question from a less idiological standpoint: I simply use river differently than I'd use sway (or anything I used before). Instead of setting up workspaces for different tasks, I set up the entire environment to fit the task I am currently in that moment working on. That allows me to activate off-topic tags (like the one with the IRC client) without actually leaving my work
<leon-p>
environment. One less context switch
<elshize>
leon-p: right, I'm used to sway type of workspaces; I am interested to try it your way though, we'll see how I feel about it.
<elshize>
I like the idea, but I might need some time to get used to it
<leon-p>
elshize: note though that the way I work is pretty chaotic, so setting up workspaces was never the right fit for me anyway, because as soon as I got back to some task after working on another for ~1hour, I already fealt like using a different layout :D
<elshize>
leon-p: I don't really use workspaces for tasks; like I got my browser on 1, my coding window(s) on 7, music app on 6, slack on 8, you get the idea...
<elshize>
but most of them I want open as a large window, like I got a tmux session with code and shell split -- I want it large.
<elshize>
but I can see myself working and then activating another tag where I have my todo list open, without switching context
<leon-p>
I get what you mean, some windows you want large, others you want small. But to me dynamic deterministic tiling means I can always easiely get every window I want to exactly the right size I want at that time. Laying things out in advance make less sense if you have all of this down to muscle memory.
<leon-p>
For example, if I wanted this window to be larger, I press Super+Enter to use rivers zoom feature and Super+L to increase the size of my main area, without even thinking about it.
<elshize>
makes sense, well, I'll experiment and see what works best for me.
<leon-p>
yeah, the big disclaimer here is as always Works For Me™, the human version of Works On My Machine™
<novakane>
tags are amazing, but it take time to see it, and we all used to workspaces so it's hard to forgrt about years of that
<elshize>
novakane: that's true, that's why I want to give it a real try before I make my mind as to what I like ;)
<novakane>
that's the right spirit
<ifreund>
rivertile mostly doesn't have layout-per-tag or separate ratio/whatnot per tag as I don't use those things and therefore don't want to maintain them
<elshize>
ifreund: that much I kinda figured :) I was just digging for why and I got my answer
novakane has quit [Quit: WeeChat 3.2]
novakane has joined #river
<novakane>
so what's mssing before river 0.1, only the cursor state thing?
<ifreund>
novakane: yeah, just that bug fix
<novakane>
cool we near to it then, gonna help a lot of people to have a stable release in distros package
<ifreund>
I also wanted to write a brief blog post introducing river
<ifreund>
I should probably start that, and if leon-p hasn't had time to finish the cursor fix by the time I've got the post ready and have prepared for my exam monday I'll finish that up too
ecocode_ has quit [Quit: Connection closed for inactivity]
<leon-p>
I should have the cursor thing ready this week. I have some code already, just haven't had the time to test it properly and to clean it up and push it.
<ifreund>
sweet
<novakane>
nice, more article on river :D
novakane_ has joined #river
novakane has quit [Quit: WeeChat 3.2]
novakane_ has quit [Quit: novakane_]
novakane has joined #river
ecocode_ has joined #river
leon-p has quit [Quit: leaving]
novakane has quit [Quit: novakane]
ecocode_ has quit [Quit: Connection closed for inactivity]