diff options
| author | fauxpark <fauxpark@gmail.com> | 2017-12-09 06:36:32 +0100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-12-09 16:46:11 +0100 |
| commit | 7b0356d1d49da6574570e110f61f95692afdb3d0 (patch) | |
| tree | a3e70802085ea8089f1e7851529f0296247fa264 /docs/feature_userspace.md | |
| parent | 6eb89ae906db7f226570e1839b88dcdd3a8fa962 (diff) | |
| download | qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.gz qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.xz | |
Convert all headings to Title Case
Diffstat (limited to 'docs/feature_userspace.md')
| -rw-r--r-- | docs/feature_userspace.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md index bbb035109..803ab5c82 100644 --- a/docs/feature_userspace.md +++ b/docs/feature_userspace.md @@ -1,4 +1,4 @@ -# Userspace: sharing code between keymaps +# Userspace: Sharing Code Between Keymaps If you use more than one keyboard with a similar keymap, you might see the benefit in being able to share code between them. Create your own folder in `users/` named the same as your keymap (ideally your github username, `<name>`) with the following structure: @@ -93,4 +93,3 @@ bool process_record_user(uint16_t keycode, keyrecord_t *record) { This will add a new `KC_MAKE` keycode that can be used in any of your keymaps. And this keycode will output `make <keyboard>:<keymap">`, making frequent compiling easier. And this will work with any keyboard and any keymap as it will output the current boards info, so that you don't have to type this out every time. Additionally, this should flash the newly compiled firmware automatically, using the correct utility, based on the bootloader settings (or default to just generating the HEX file). However, it should be noted that this may not work on all systems. AVRDUDE doesn't work on WSL, namely (and will dump the HEX in the ".build" folder instead). - |