summaryrefslogtreecommitdiffstats
path: root/docs/feature_macros.md
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2018-05-07 22:40:57 -0700
committerskullydazed <skullydazed@users.noreply.github.com>2018-05-07 22:46:26 -0700
commit303f425c6b4f9ab6056f863e515c71c9325f2bfa (patch)
tree150c9eba72bc40cf2d9a101d4a606156ea54cd0b /docs/feature_macros.md
parent9e5676650ec4ae71565201871c1aaf05e96a756b (diff)
Fix up info boxes.
Diffstat (limited to 'docs/feature_macros.md')
-rw-r--r--docs/feature_macros.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/docs/feature_macros.md b/docs/feature_macros.md
index 006fa04bca..6731530812 100644
--- a/docs/feature_macros.md
+++ b/docs/feature_macros.md
@@ -2,9 +2,7 @@
Macros allow you to send multiple keystrokes when pressing just one key. QMK has a number of ways to define and use macros. These can do anything you want: type common phrases for you, copypasta, repetitive game movements, or even help you code.
-{% hint style='danger' %}
-**Security Note**: While it is possible to use macros to send passwords, credit card numbers, and other sensitive information it is a supremely bad idea to do so. Anyone who gets a hold of your keyboard will be able to access that information by opening a text editor.
-{% endhint %}
+!> **Security Note**: While it is possible to use macros to send passwords, credit card numbers, and other sensitive information it is a supremely bad idea to do so. Anyone who gets a hold of your keyboard will be able to access that information by opening a text editor.
## The New Way: `SEND_STRING()` & `process_record_user`
@@ -132,9 +130,7 @@ SEND_STRING(".."SS_TAP(X_END));
## The Old Way: `MACRO()` & `action_get_macro`
-{% hint style='info' %}
-This is inherited from TMK, and hasn't been updated - it's recommend that you use `SEND_STRING` and `process_record_user` instead.
-{% endhint %}
+?> This is inherited from TMK, and hasn't been updated - it's recommend that you use `SEND_STRING` and `process_record_user` instead.
By default QMK assumes you don't have any macros. To define your macros you create an `action_get_macro()` function. For example: