diff options
author | Ryan <fauxpark@gmail.com> | 2022-10-20 22:20:07 +1100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-10-20 12:20:07 +0100 |
commit | c347e732be6b50500c1651b3fb8c0753b0c9c40d (patch) | |
tree | 4212f78e0825d1910516a8331287fd7236f8216a /docs/feature_eeprom.md | |
parent | 35f1cd0ec47d95cf20d9dec91ad46b7b4295982f (diff) |
Remove legacy EEPROM clear keycodes (#18782)
* `EEP_RST` -> `EE_CLR`, default-ish keymaps
* `EEP_RST` -> `EE_CLR`, user keymaps
* `EEP_RST` -> `EE_CLR`, community layouts
* `EEP_RST` -> `EE_CLR`, userspace
* `EEP_RST` -> `EE_CLR`, docs & core
Diffstat (limited to 'docs/feature_eeprom.md')
-rw-r--r-- | docs/feature_eeprom.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_eeprom.md b/docs/feature_eeprom.md index e261c455cb..3a4119eab7 100644 --- a/docs/feature_eeprom.md +++ b/docs/feature_eeprom.md @@ -109,7 +109,7 @@ bool process_record_user(uint16_t keycode, keyrecord_t *record) { } } ``` -And lastly, you want to add the `eeconfig_init_user` function, so that when the EEPROM is reset, you can specify default values, and even custom actions. To force an EEPROM reset, use the `EEP_RST` keycode or [Bootmagic Lite](feature_bootmagic.md) functionallity. For example, if you want to set rgb layer indication by default, and save the default valued. +And lastly, you want to add the `eeconfig_init_user` function, so that when the EEPROM is reset, you can specify default values, and even custom actions. To force an EEPROM reset, use the `EE_CLR` keycode or [Bootmagic Lite](feature_bootmagic.md) functionallity. For example, if you want to set rgb layer indication by default, and save the default valued. ```c void eeconfig_init_user(void) { // EEPROM is getting reset! |