moergo-sc / glove80-zmk-config Goto Github PK

I tried out this config on my other keyboard and it works much much better than the default way of handling homerow mods https://github.com/urob/zmk-config#timeless-homerow-mods.

Would like to request that this is added to glove80 zmk config.

I noticed that you are using nix to build the keyboard firmware.
I tried to replicate what the github CI does locally and it seems to work fine.
I cannot test it on the keyboard because I have not yet received it.

What I did:

git clone https://github.com/moergo-sc/glove80-zmk-config.git
cd glove80-zmk-config
git clone https://github.com/moergo-sc/zmk src
nix-build config -o combined

This has properly generated combined/glove80.uf2.

My question is the following: is there any problem with doing this locally instead of relying on GitHub ?
I can't think of any reason why it wouldn't work.

Dlsclaimer: noob.

Curious what's the difference between glove80-zmk-config using Nix toolchain and glove80-zmk-config-west? Obviously the latter uses west toolchain but beyond that how would you determine which to use (even if it simply comes down to differences in toolchains if all else is equal)?

For example, ZMK/Zephyr uses west but AFAIK this repo is the official ZMK config repo for the Glove80. Is there any advantages to using west assuming firmware is built via Docker (I assume if built locally/natively sticking with the "unofficial" glove80-zmk-config-west reduces dependencies on the system). I would also think the other glove80-zmk-config-west repo using the same toolchain as ZMK might be better served as the default "official" repo? But it seems this repo is clearly more popular based on the stars count on the repo.

I assume you don't need to use NixOS to use Nix toolchain--are there any benefits to preferring Nix over west?

I realize it ultimately doesn't matter which toolchains you use as they both build the same thing and also a lot of this is probably opinionated--I'm just hoping to learn.

I think there may be an issue with cachix-actions. I am seeing this error when trying to build.

Hey 👋 Just copied this template to start building out my own keymap and noticed the first GitHub Actions run spat out some warnings for Node 16 actions being deprecated and recommending moving to Node 20 actions.

Small patch on my copy resolves the warnings and seems to work just fine. Might be nice to reproduce on your end so that people copying it fresh don't get those warnings.