Currently, I have the commits in my qmk_firmware branch organised by commit-per-folder. (e.g. 'add userspace' is 1 commit, as is 'add keyboard pykey40').
Syncing, with two changes:
adjusting the leader-key sequences that I use (defined in userspace rgoulter.c). -- I wasn't using the other leader sequences. The new ones are: reboot (LEAD q b), capslock/caps word (LEAD c c, LEAD c w), and setting 'OS' for desktop shortcuts (LEAD o w, LEAD o l, LEAD o m).
I made an attempt at "set keymap", but ... the qmk combos (chords) are based on key; so, changing default layer to QWERTY doesn't quite work. Currently, I use ;q as LEAD (since this is Dvorak bottom row), but QWERTY, the ; is on a tap-hold key.. and these keys aren't adjacent. -- Might be able to 'hack' this by making use of the default layer callback, to update the chords?
Other things which might be useful: managing RGB (toggle/on/off, set to fav. theme, random), managing haptics.
formatting the C files per the editorconfig / clang format in qmk_firmware.
Currently, I have the commits in my
qmk_firmware
branch organised by commit-per-folder. (e.g. 'add userspace' is 1 commit, as is 'add keyboard pykey40').Syncing, with two changes:
adjusting the leader-key sequences that I use (defined in userspace
rgoulter.c
). -- I wasn't using the other leader sequences. The new ones are: reboot (LEAD q b
), capslock/caps word (LEAD c c
,LEAD c w
), and setting 'OS' for desktop shortcuts (LEAD o w
,LEAD o l
,LEAD o m
).;q
as LEAD (since this is Dvorak bottom row), but QWERTY, the;
is on a tap-hold key.. and these keys aren't adjacent. -- Might be able to 'hack' this by making use of the default layer callback, to update the chords?formatting the C files per the editorconfig / clang format in qmk_firmware.