summaryrefslogtreecommitdiff
path: root/docs/feature_userspace.md
diff options
context:
space:
mode:
authorRyan <fauxpark@gmail.com>2020-12-11 13:45:24 +1100
committerGitHub <noreply@github.com>2020-12-11 13:45:24 +1100
commit501f2fdef115314713e94428d409e5c3b5bfc1c2 (patch)
treee454192658ed0000d1d814e2eab492410febe98f /docs/feature_userspace.md
parent5b5d74a2677c281d12cd69825d2e252842786667 (diff)
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.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md
index 77a6c8d762..8b001e3ce2 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
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
-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.
+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.
Once you've done that, you'll want to set the keycode definitions that you need to the `<name>.h` file. For instance:
```c