diff options
author | Nick Brassel <nick@tzarc.org> | 2021-01-28 10:52:59 +1100 |
---|---|---|
committer | Nick Brassel <nick@tzarc.org> | 2021-01-28 10:52:59 +1100 |
commit | d65db68f9f2614b91e3cb565086166b01400e473 (patch) | |
tree | 7477dbd7666a170444ffbf2ad29aa6d25189bf50 /docs | |
parent | 99f3df28939d89b7fc2d2e7c0ee21b0879c7813f (diff) | |
parent | bad9592a18494e3f678c2a117a526ca5f2f2280d (diff) |
Merge remote-tracking branch 'upstream/master' into develop
Diffstat (limited to 'docs')
-rw-r--r-- | docs/feature_rgblight.md | 1 | ||||
-rw-r--r-- | docs/newbs_getting_started.md | 2 |
2 files changed, 3 insertions, 0 deletions
diff --git a/docs/feature_rgblight.md b/docs/feature_rgblight.md index c49c308d1e..b5a2b179d6 100644 --- a/docs/feature_rgblight.md +++ b/docs/feature_rgblight.md @@ -370,6 +370,7 @@ rgblight_sethsv(HSV_GREEN, 2); // led 2 |`rgblight_step_noeeprom()` |Change the mode to the next RGB animation in the list of enabled RGB animations (not written to EEPROM) | |`rgblight_step_reverse()` |Change the mode to the previous RGB animation in the list of enabled RGB animations | |`rgblight_step_reverse_noeeprom()` |Change the mode to the previous RGB animation in the list of enabled RGB animations (not written to EEPROM) | +|`rgblight_reload_from_eeprom()` |Reload the effect configuration (enabled, mode and color) from EEPROM | #### effects mode disable/enable |Function |Description | diff --git a/docs/newbs_getting_started.md b/docs/newbs_getting_started.md index 1c72911d92..3cb63e5692 100644 --- a/docs/newbs_getting_started.md +++ b/docs/newbs_getting_started.md @@ -168,6 +168,8 @@ Once that completes, re-run `qmk setup` to complete the setup and checks. <!-- tabs:end --> +?> The qmk home folder can be specified at setup with `qmk setup -H <path>`, and modified afterwards using the [cli configuration](cli_configuration.md?id=single-key-example) and the variable `user.qmk_home`. For all available options run `qmk setup --help`. + ?> If you already know [how to use GitHub](getting_started_github.md), we recommend that you create your own fork and use `qmk setup <github_username>/qmk_firmware` to clone your personal fork. If you don't know what that means you can safely ignore this message. ## 4. Test Your Build Environment |