Nick Brassel
Nick Brassel
We'll be moving towards a decoupled model with `ENCODER_DRIVER = xxxx` instead of continuing here.
`register-python-argcomplete --no-defaults qmk` should suffice. It's been in the firmware repo for 2 years, now.
I'd say your best bet at this point is to make a PR -- I'd imagine most of the team would view this as low priority as it's a nice-to-have...
I have some concerns: * As it stands, the Windows build has random modifications to files and does not compile * I see no reason why we would want to...
This PR is on hold until #24085 is rectified.
As of August 26, 2024, `qmk/qmk_firmware` is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control. As you've submitted a PR...
As of August 26, 2024, `qmk/qmk_firmware` is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control. As you've submitted a PR...
As of August 26, 2024, `qmk/qmk_firmware` is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control. As you've submitted a PR...
As of August 26, 2024, `qmk/qmk_firmware` is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control. As you've submitted a PR...
As of August 26, 2024, `qmk/qmk_firmware` is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control. As you've submitted a PR...