It was e for edge, now k for keys. Why? I'm toying with ideas
for a full Tutte Coxeter graph (30 vertices/nodes/GPIO pins,
45 edges/switches) incuding 42 keys plus a rotary encoder
(these act like three switches: clockwise, anticlockwise,
press - so 42 edges for normal keys + 3 edges for a rotary
encoder gives 42 + 3 = 45 edges) which could be named with
suffix 43ke.
❯ qmk new-keyboard -kbtutte_coxeter_c36e -n "Peter J. A. Cock" -u peterjc -t RP2040 -l split_3x5_3
Ψ Generating a new QMK keyboard directory
Ψ Created a new keyboard called tutte_coxeter_36e.
Ψ Build Command: qmk compile -kb tutte_coxeter_36e -km default.
Ψ Project Location: /Users/peterjc/repositories/qmk_firmware/keyboards/tutte_coxeter_36e.
Ψ Now update the config files to match the hardware!
❯ mv ~/repositories/qmk_firmware/keyboardstutte_coxeter_36e ~/repositories/qmk_userspace/keyboards
Note it did not want to accept hyphens, so used underscores.
Then define sparse 13x13 scanning matrix of 36 edge / 26 vertice graph,
using the RP2040 GPIO pin names.
i.e. The partial Tutte-Coxeter graph, using RP2040 GPIO pin names.
This is needed to support VS Code with clangd for userspace keymaps (in
this case `compile_commands.json` and `.cache/clangd` are located in the
`qmk_userspace` working copy).
- folder name inside dev container is same as folder name on host
so if it differs from qmk_userspace then setup.sh cannot be found
and it sets incorrect user.overlay_dir
- docs https://containers.dev/implementors/json_reference/