<novakane>
damn everything in one file, not easy to read
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
<pkap>
I'm trying to fix my mess with ifreunds instructions. After `git reset --hard <fixed_branch>`, locally everything is fixed. But how do I get it to the github branch? Git hints that I need to pull first, but then I recreate the mess =L
<tiosgz`>
push --force-with-lease?
<pkap>
Yeah it worked! Thanks tiosgz`!
<novakane>
looks like the ci works great for PR too, cool
snakedye has quit [Ping timeout: 256 seconds]
snakedye has joined #river
voroskoi has joined #river
elshize has quit [Ping timeout: 250 seconds]
elshize has joined #river
voroskoi[m] has left #river [#river]
<pkap>
How much CI time is available for river on Sourcehut? I feel a bit bad for causing so many builds with my PR...
<leon-p>
pkap: I would not worry about that. The amount of PRs per month is so low that it's pretty unlikely that one will have a noticeable impact on the resources allocated for river or that river is having a noticeable impact on sourcehut.
<pkap>
Nice. So Sourcehut does not limit to a certain amount of minutes like gitlab/github does?
<leon-p>
pkap: I don't think they do, at least I can not find anything in the docs. However builds require a paid account.
<novakane>
like with initCapacity(util.gpa, 2) instead of ensureTotalCapacity(2)
waleee has joined #river
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 245 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Remote host closed the connection]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
pkap has joined #river
<leon-p>
I am kinda starting to miss the "auto-back-and-forth" feature from Sway; Not sure if that can be implemented as a separate client though...
<novakane>
what's that?
<leon-p>
novakane: If you focus a tag, and then try to focus the tag again while you are still on it, it automagically sends you back to your previous tag. Super handy because it means you don't have to remember where you came from.
mon_aaraj has quit [Ping timeout: 260 seconds]
<leon-p>
although I think it can probably be done client-side, maybe if I have some time later
<novakane>
ah yeah, that's nice, would be cool
mon_aaraj has joined #river
* tiosgz`
wonders why one would need to remember where they came from if they know where they want to go :P
<novakane>
yeah maybe with river-status protocol like getting the previous tags and then comparing with the new one
<leon-p>
:P
<leon-p>
when I do a lab report, I have to cross-check at least four or five different documents, and it's always nicer if I can bounce back to my text editor without having to remember where I parked it.
elshize has quit [Ping timeout: 256 seconds]
elshize has joined #river
mon_aaraj has quit [Ping timeout: 250 seconds]
mon_aaraj has joined #river
<waleee>
isn't it more tag-like (well, default in dwm) to have it on mod+tab ?
<leon-p>
it certainly possible, but it requires to think about one additional keybind, so it has a higher cognitive load.
<waleee>
some combination of ___+tab is usual for similar behaviour in some common apps (mainly browsers)
<waleee>
it's more uncommon with the sway behaviour afaik
<leon-p>
how common something is is not a good indicator of its quality, I find
<waleee>
sure
<waleee>
but it was mostly a counterpoint to "additional keybind, so it has a higher cognitive load"
<waleee>
since you would be aware of a similar keybinding in other contexts
<leon-p>
In fact I already have Super+Tab bound to rivers back-and-forth feature, but I still think it would be nicer to just re-use the tag keybind
<waleee>
it shouldn't be too hard to add the sway-way I guess? I'd imagine an if or additional switch-case
<waleee>
or is it specified in a protocol?
<leon-p>
it'd be a rather trivial patch, but I am also not a huge fan of stacking too many features onto river, so I think I'll just write a helper client until the layout generators turn into proper window managers