diff options
author | Ryan <fauxpark@gmail.com> | 2020-12-11 13:45:24 +1100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-12-11 13:45:24 +1100 |
commit | 501f2fdef115314713e94428d409e5c3b5bfc1c2 (patch) | |
tree | e454192658ed0000d1d814e2eab492410febe98f /docs/feature_userspace.md | |
parent | 5b5d74a2677c281d12cd69825d2e252842786667 (diff) | |
download | qmk_firmware-501f2fdef115314713e94428d409e5c3b5bfc1c2.tar.gz qmk_firmware-501f2fdef115314713e94428d409e5c3b5bfc1c2.zip |
Normalise include statements in core code (#11153)
* Normalise include statements in core code
* Missed one
Diffstat (limited to 'docs/feature_userspace.md')
-rw-r--r-- | docs/feature_userspace.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md index 77a6c8d76..8b001e3ce 100644 --- a/docs/feature_userspace.md +++ b/docs/feature_userspace.md | |||
@@ -184,7 +184,7 @@ If you wanted to consolidate macros and other functions into your userspace for | |||
184 | 184 | ||
185 | First, you'd want to go through all of your `keymap.c` files and replace `process_record_user` with `process_record_keymap` instead. This way, you can still use keyboard specific codes on those boards, and use your custom "global" keycodes as well. You'll also want to replace `SAFE_RANGE` with `NEW_SAFE_RANGE` so that you wont have any overlapping keycodes | 185 | First, you'd want to go through all of your `keymap.c` files and replace `process_record_user` with `process_record_keymap` instead. This way, you can still use keyboard specific codes on those boards, and use your custom "global" keycodes as well. You'll also want to replace `SAFE_RANGE` with `NEW_SAFE_RANGE` so that you wont have any overlapping keycodes |
186 | 186 | ||
187 | Then add `#include <name.h>` to all of your keymap.c files. This allows you to use these new keycodes without having to redefine them in each keymap. | 187 | Then add `#include "<name>.h"` to all of your keymap.c files. This allows you to use these new keycodes without having to redefine them in each keymap. |
188 | 188 | ||
189 | Once you've done that, you'll want to set the keycode definitions that you need to the `<name>.h` file. For instance: | 189 | Once you've done that, you'll want to set the keycode definitions that you need to the `<name>.h` file. For instance: |
190 | ```c | 190 | ```c |