13:16 <uncomfyhalomacro> dnkl. are your projects moving from codeberg to sourcehut? just asking for confirmation since I packaged most of your tools in openSUSE.

13:18 <dnkl> uncomfyhalomacro: no, but I'm using it as a mirror, and to use their CI

13:20 <uncomfyhalomacro> oh cool. thanks!

18:30 <LemanR> hey all, quick Q&A. Should this command work

18:30 <LemanR> riverctl map normal Super+Alt Left send-layout-cmd rivertile "main#-ratio -0.05"

18:30 <LemanR> wait I see the typo

18:31 <LemanR> the # after main, I was moving things around and making things into comments and what not

18:34 <LemanR> These two arn't working but am I right to assume it's because I am attempting to use symbols instead of letters?

18:34 <LemanR> riverctl map normal Super+Alt = send-layout-cmd rivertile "main-count +1"

18:34 <LemanR> riverctl map normal Super+Alt - send-layout-cmd rivertile "main-count -1"

18:36 <LemanR> nvm, I think the assumption is correct, if this is bash script then I probably shouldn't be able to use = and - like I am attempting here

18:36 <gbrlsnchs> I think it's Equal and Minus respectively, but I'm not 100% sure

18:37 <LemanR> wonder if I can escape in this config so replacing = with \= and what not

18:38 <gbrlsnchs> I don't think so

18:39 <gbrlsnchs> almost sure you need to use the respective key names

19:02 <LemanR> i didn't consider that option, probably the most obvious option but I don't work in any software field so it didn't occur to me lol

19:07 <LemanR> btw, can I use tho names listed in xkbcommon-keysyms.h file? this is the file that defines xkb_key names as that other number (for example the 'other number' 0xff60 is defined as XKB_KEy_Select) so in my script can I use XKB_KEY_Select as the name or do I have to go to a different file to find the name. I'd rather use the XKB version as it has the

19:07 <LemanR> number with it and I believe those numbers work as well as I've been using those

19:11 <LemanR> guess I can take a command that already works and try the xkb name to see if I can use that name.

19:11 <n0r> LemanR: Man riverctl says "Keys are specified by their XKB keysym name. See /usr/include/xkbcommon/xkbcommon-keysyms.h for the complete list."

19:12 <novakane> you can also use wev to get the name https://git.sr.ht/~sircmpwn/wev

19:13 <LemanR> That's weird because I can use some other version of the name. For example instead of needing to type XKB_KEY_RETURN I have a command that simply has Return which also works.

19:15 <LemanR> that's why I was wondering, btw the river github was where I first got introduced to this keysyms file which is apparently very useful to have so thanks for having this in the github :D

19:15 <LemanR> brb restarting river real quick

19:21 <LemanR> this is where I get confused with the naming. this does not work

19:21 <LemanR> riverctl map normal Super+Alt XKB_KEY_Return zoom

19:21 <LemanR> but

19:21 <LemanR> riverctl map normal Super+Alt Return zoom

19:21 <LemanR> does work

19:23 <LemanR> the first one (the longer name) is how my keysym file shows the name of the return key, not the shorter version. Does bash 'chop off' the XKB_KEY_ part when someone uses bash?

19:26 <LemanR> sorry if this seems nit-picky but knowing exactly what names are going to work in this config file (which is just a bash script so I assume should just follow bash scripting rules) avoids confusing when understanding how this software is working.

19:30 <novakane> LemanR: that is just how xkbxommon names works afaik, just use name without the prefix or use wev

19:34 <LemanR> @novakane so for my learning, will this naming convention be language specific (like some languages like Bash 'want' Return instead of XKB_KEY_Return when coding, while other languages 'want' the long version instead?)

19:35 <LemanR> granting/assuming the language in question uses the keysym.h file lol

19:37 <novakane> bash doesn't really use anything, afaik that is the officials name use everywhere for configuration but river does the translation of the key codes

19:38 <LemanR> omg just found out I can change individual commands by just typing them into the terminal XD love the feature (I know I have to put them in init it make it persistent)

20:02 <LemanR> but the bash thing is just confusing, I'll dive down that rabbit whole when I have more time lol

20:02 <LemanR> for now I know how to use the naming convention for what I'm doing so we good lol