12:22 <ThatGuestAgain> Hi. Currently `map` can only be used to map one river action. For doing multiple, one needs to do a roundtrip through a script. Is extending mapping to multiple actions feasible? Usecase examples:

12:22 <ThatGuestAgain>  - moving both view and focus to another tag

12:22 <ThatGuestAgain>  - snapping a view and immediately moving it, to move it to a specific position (potentially in both dimensions at once)

12:22 <ThatGuestAgain>  - immediately leaving the mappings mode so it doesn't need to be done manually

12:22 <ThatGuestAgain> All of these are possible with small extra scripts. My issue is not so much the roundtrip to the shell, I do not notice latency or timing issues. Having an extra file for each in-a-mode command however is annoying to deal with, edit, check for collisions etc.

12:38 <tiosgz> ThatGuestAgain: you can just write the stuff inline, like ... spawn 'riverctl foo; riverctl baz'

12:40 <tiosgz> or i've made a simple riverctl fork some time ago that you could spawn too https://codeberg.org/tiosgz/riverctlseq

12:41 <tiosgz> just note that it really only runs several river commands, so you indeed want to ... spawn 'riverctlseq ...'

12:42 <ThatGuestAgain> Oh. I am dumb. I can even shorten the returning to normal mode with string interpolation... My apologies for not thinking this through : /

12:48 <Seli> is there any way i can execute multiple commands from a single key map?

12:48 <Seli> I am wanting to close and then run a shell command

12:49 <ThatGuestAgain> Lol I just asked basically the same. Look at the log Seli

12:49 <Seli> whoops, sorry! will do :)

14:10 <leon-p> I think keybinds will be outsourced to the layout generators / WMs anyway, so all of this is up to change

18:49 <TheAnachron> Hello, it's been ages.

18:52 <TheAnachron> I see that river is now depending on zig0.12. Gotta update my build templates for it.

18:56 <TheAnachron> there are a ton of great changes, neat! is there any breaking change since the river-git master from 4 months ago? I would probably not update right now then

19:07 <TheAnachron> Void Linux only got wlroots 0.17, but river requires 0.17.2 on 0.3.2. Yet the build suceeded. Should it work nonetheless?

19:08 <novakane> I don't think there have been breaking changes recently but you probably need to check the commits log to be sure

19:08 <TheAnachron> shouldn't breaking changes be announced via https://codeberg.org/river/river/releases/? That's what I checked.

19:11 <novakane> sure, but you were talking about comparing with a master version of some months ago not 0.2.6

19:12 <TheAnachron> that's right. you are talking about a change that was reverted on master without being ever in a release?

19:15 <novakane> no, I'm saying that the breaking changes on the release page are between two tagged versions, not between your version from a random commit 4 months ago

19:17 <novakane> and I'm saying that I don't think there have been breaking changes since 4 months ago

19:27 <TheAnachron> okay thanks, nothing I was able to find so far. I guess the minor version difference on wlroots shouldnt matter?

19:28 <vyivel> wlroots patch releases are compatible with each other