00:29 <tleydxdy[m]> ifreund: thanks for the hide cursor fix. can you also take a look at fixing spawn-tagmask? it will get lost when the monitor goes to sleep or otherwise turned off. I can't figure out how to fix that :(

18:52 <pkap> ifreund: I implemented the layout-pinned mappings that we discussed yesterday.

18:53 <pkap> In a basic fashion https://github.com/riverwm/river/pull/577/files

18:53 <ifreund> pkap: wow, you are so fast! Thanks for your patience with the constantly changing goals for this interface :D

18:56 <pkap> Some things need more discussion though :)

18:56 <ifreund> I've gotta make and eat some dinner before I have a look, will get back to you soon

19:03 <pkap> Np, there's no rush :)

19:30 <dnkl> layout-independent mappings... have fun! 😂

19:30 <dnkl> /me remembers implementing it for foot

19:30 <dnkl> wait what... goguma doesn't support /me?

19:32 <pkap> dnkl: how did you solve it?

19:34 <dnkl> pkap: there are two parts. One, when a new keymapp is received, figure out which keycodes generate the symbol(s) from the user's key bindings: https://codeberg.org/dnkl/foot/src/commit/e4d085a17b4b82e7b20572b63898bfb0b55ddc2c/key-binding.c#L221

19:36 <dnkl> then, when matching key pressed, figure out the untranslated symbol (that is, the level 0 symbol, for the pressed key), and map it against the "raw" keycodes: https://codeberg.org/dnkl/foot/src/commit/e4d085a17b4b82e7b20572b63898bfb0b55ddc2c/input.c#L1372

19:37 <dnkl> hmm, sorry, mixed things up a bit... the last comment should be:

19:38 <dnkl> when matching key pressed, ignore the symbol, and just map the raw keycode against the keycodes we found in step 1

19:38 <dnkl> s/pressed/presses

19:52 <pkap40> dnkl: Ah yeah, this is similiar to what we want to do :)

19:59 <dnkl> pkap40: I'm guessing you'll want/need the logic for "untranslated" symbols as well

20:08 <pkap> dnkl: Yes correct, we have that :)

20:15 <pkap> One question I'm thinking about here is should we prioritize "translated" over "raw" mappings or whichever is matched first.

20:24 <pkap> E.g.: One could have two different mappings that are triggered by the same combination, like `Super+Shift 1` and `Super Exclam`. Previously, I prioritized the latter, meaning we needed looping twice over all mappings.

22:18 <tleydxdy[m]> maybe raise a error when binding the second one?

22:29 <tleydxdy[m]> since that is most certainly by mistake