Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.