diff options
| author | Joel Challis <git@zvecr.com> | 2021-07-25 17:18:09 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-25 17:18:09 +0100 |
| commit | fc9fb2c77505cf1dcf5d1f50dd61a980471b3494 (patch) | |
| tree | 3dce233f23dbe991c4dee0a63eb4dc0fe9c2b6f5 /docs/faq_debug.md | |
| parent | b69e7431aa2e22b4f4662c64e84ed242caac055e (diff) | |
Allow output of logging when running unit tests (#13556)
* Initial pass at enabling logging for unit tests
* Add to docs
* Bind debug for more test types
* Force everything
* Tidy up slightly
Diffstat (limited to 'docs/faq_debug.md')
| -rw-r--r-- | docs/faq_debug.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq_debug.md b/docs/faq_debug.md index 13a649bfa2..1afa38a624 100644 --- a/docs/faq_debug.md +++ b/docs/faq_debug.md @@ -28,7 +28,7 @@ For compatible platforms, [QMK Toolbox](https://github.com/qmk/qmk_toolbox) can Prefer a terminal based solution? [hid_listen](https://www.pjrc.com/teensy/hid_listen.html), provided by PJRC, can also be used to display debug messages. Prebuilt binaries for Windows,Linux,and MacOS are available. -## Sending Your Own Debug Messages +## Sending Your Own Debug Messages :id=debug-api Sometimes it's useful to print debug messages from within your [custom code](custom_quantum_functions.md). Doing so is pretty simple. Start by including `print.h` at the top of your file: |