3 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.
5 !> **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.
7 ## The New Way: `SEND_STRING()` & `process_record_user`
9 Sometimes you just want a key to type out words or phrases. For the most common situations we've provided `SEND_STRING()`, which will type out your string (i.e. a sequence of characters) for you. All ASCII characters that are easily translated to a keycode are supported (e.g. `\n\t`).
11 Here is an example `keymap.c` for a two-key keyboard:
14 enum custom_keycodes {
18 bool process_record_user(uint16_t keycode, keyrecord_t *record) {
21 if (record->event.pressed) {
22 // when keycode QMKBEST is pressed
23 SEND_STRING("QMK is the best thing ever!");
25 // when keycode QMKBEST is released
33 const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
40 What happens here is this:
41 We first define a new custom keycode in the range not occupied by any other keycodes.
42 Then we use the `process_record_user` function, which is called whenever a key is pressed or released, to check if our custom keycode has been activated.
43 If yes, we send the string `"QMK is the best thing ever!"` to the computer via the `SEND_STRING` macro (this is a C preprocessor macro, not to be confused with QMK macros).
44 We return `true` to indicate to the caller that the key press we just processed should continue to be processed as normal (as we didn't replace or alter the functionality).
45 Finally, we define the keymap so that the first button activates our macro and the second button is just an escape button.
47 You might want to add more than one macro.
48 You can do that by adding another keycode and adding another case to the switch statement, like so:
51 enum custom_keycodes {
57 bool process_record_user(uint16_t keycode, keyrecord_t *record) {
60 if (record->event.pressed) {
61 // when keycode QMKBEST is pressed
62 SEND_STRING("QMK is the best thing ever!");
64 // when keycode QMKBEST is released
68 if (record->event.pressed) {
69 // when keycode QMKURL is pressed
70 SEND_STRING("https://qmk.fm/" SS_TAP(X_ENTER));
72 // when keycode QMKURL is released
76 if (record->event.pressed) {
77 SEND_STRING(SS_LCTRL("ac")); // selects all and copies
84 const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
86 {MY_CUSTOM_MACRO, MY_OTHER_MACRO}
93 You may want to use keys in your macros that you can't write down, such as `Ctrl` or `Home`.
94 You can send arbitrary keycodes by wrapping them in:
96 * `SS_TAP()` presses and releases a key.
97 * `SS_DOWN()` presses (but does not release) a key.
98 * `SS_UP()` releases a key.
102 SEND_STRING(SS_TAP(X_HOME));
104 Would tap `KC_HOME` - note how the prefix is now `X_`, and not `KC_`. You can also combine this with other strings, like this:
106 SEND_STRING("VE"SS_TAP(X_HOME)"LO");
108 Which would send "VE" followed by a `KC_HOME` tap, and "LO" (spelling "LOVE" if on a newline).
110 There's also a couple of mod shortcuts you can use:
118 These press the respective modifier, send the supplied string and then release the modifier.
119 They can be used like this:
121 SEND_STRING(SS_LCTRL("a"));
123 Which would send LCTRL+a (LCTRL down, a, LCTRL up) - notice that they take strings (eg `"k"`), and not the `X_K` keycodes.
125 ### Alternative Keymaps
127 By default, it assumes a US keymap with a QWERTY layout; if you want to change that (e.g. if your OS uses software Colemak), include this somewhere in your keymap:
129 #include <sendstring_colemak.h>
131 ### Strings in Memory
133 If for some reason you're manipulating strings and need to print out something you just generated (instead of being a literal, constant string), you can use `send_string()`, like this:
136 char my_str[4] = "ok.";
140 The shortcuts defined above won't work with `send_string()`, but you can separate things out to different lines if needed:
143 char my_str[4] = "ok.";
144 SEND_STRING("I said: ");
146 SEND_STRING(".."SS_TAP(X_END));
150 ## Advanced Macro Functions
152 There are some functions you may find useful in macro-writing. Keep in mind that while you can write some fairly advanced code within a macro, if your functionality gets too complex you may want to define a custom keycode instead. Macros are meant to be simple.
154 ### `record->event.pressed`
156 This is a boolean value that can be tested to see if the switch is being pressed or released. An example of this is
159 if (record->event.pressed) {
166 ### `register_code(<kc>);`
168 This sends the `<kc>` keydown event to the computer. Some examples would be `KC_ESC`, `KC_C`, `KC_4`, and even modifiers such as `KC_LSFT` and `KC_LGUI`.
170 ### `unregister_code(<kc>);`
172 Parallel to `register_code` function, this sends the `<kc>` keyup event to the computer. If you don't use this, the key will be held down until it's sent.
174 ### `tap_code(<kc>);`
176 This will send `register_code(<kc>)` and then `unregister_code(<kc>)`. This is useful if you want to send both the press and release events ("tap" the key, rather than hold it).
178 If you're having issues with taps (un)registering, you can add a delay between the register and unregister events by setting `#define TAP_CODE_DELAY 100` in your `config.h` file. The value is in milliseconds.
180 ### `register_code16(<kc>);`, `unregister_code16(<kc>);` and `tap_code16(<kc>);`
182 These functions work similar to their regular counterparts, but allow you to use modded keycodes (with Shift, Alt, Control, and/or GUI applied to them).
184 Eg, you could use `register_code16(S(KC_5));` instead of registering the mod, then registering the keycode.
186 ### `clear_keyboard();`
188 This will clear all mods and keys currently pressed.
192 This will clear all mods currently pressed.
194 ### `clear_keyboard_but_mods();`
196 This will clear all keys besides the mods currently pressed.
202 This macro will register `KC_LALT` and tap `KC_TAB`, then wait for 1000ms. If the key is tapped again, it will send another `KC_TAB`; if there is no tap, `KC_LALT` will be unregistered, thus allowing you to cycle through windows.
205 bool is_alt_tab_active = false; # ADD this near the begining of keymap.c
206 uint16_t alt_tab_timer = 0; # we will be using them soon.
208 enum custom_keycodes { # Make sure have the awesome keycode ready
209 ALT_TAB = SAFE_RANGE,
212 bool process_record_user(uint16_t keycode, keyrecord_t *record) {
213 switch (keycode) { # This will do most of the grunt work with the keycodes.
215 if (record->event.pressed) {
216 if (!is_alt_tab_active) {
217 is_alt_tab_active = true;
218 register_code(KC_LALT);
220 alt_tab_timer = timer_read();
221 register_code(KC_TAB);
223 unregister_code(KC_TAB);
230 void matrix_scan_user(void) { # The very important timer.
231 if (is_alt_tab_active) {
232 if (timer_elapsed(alt_tab_timer) > 1000) {
233 unregister_code16(LALT(KC_TAB));
234 is_alt_tab_active = false;
242 ## **(DEPRECATED)** The Old Way: `MACRO()` & `action_get_macro`
244 !> This is inherited from TMK, and hasn't been updated - it's recommended that you use `SEND_STRING` and `process_record_user` instead.
246 By default QMK assumes you don't have any macros. To define your macros you create an `action_get_macro()` function. For example:
249 const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) {
250 if (record->event.pressed) {
253 return MACRO(D(LSFT), T(H), U(LSFT), T(I), D(LSFT), T(1), U(LSFT), END);
255 return MACRO(D(LSFT), T(B), U(LSFT), T(Y), T(E), D(LSFT), T(1), U(LSFT), END);
262 This defines two macros which will be run when the key they are assigned to is pressed. If instead you'd like them to run when the key is released you can change the if statement:
264 if (!record->event.pressed) {
268 A macro can include the following commands:
270 * I() change interval of stroke in milliseconds.
273 * T() type key(press and release).
274 * W() wait (milliseconds).
277 ### Mapping a Macro to a Key
279 Use the `M()` function within your keymap to call a macro. For example, here is the keymap for a 2-key keyboard:
282 const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
288 const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) {
289 if (record->event.pressed) {
292 return MACRO(D(LSFT), T(H), U(LSFT), T(I), D(LSFT), T(1), U(LSFT), END);
294 return MACRO(D(LSFT), T(B), U(LSFT), T(Y), T(E), D(LSFT), T(1), U(LSFT), END);
301 When you press the key on the left it will type "Hi!" and when you press the key on the right it will type "Bye!".
303 ### Naming Your Macros
305 If you have a bunch of macros you want to refer to from your keymap while keeping the keymap easily readable you can name them using `#define` at the top of your file.
311 const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
321 ### Single-Key Copy/Paste
323 This example defines a macro which sends `Ctrl-C` when pressed down, and `Ctrl-V` when released.
326 const macro_t *action_get_macro(keyrecord_t *record, uint8_t id, uint8_t opt) {
329 if (record->event.pressed) {
330 return MACRO( D(LCTL), T(C), U(LCTL), END );
332 return MACRO( D(LCTL), T(V), U(LCTL), END );