Macro recording optional

Name the keys and WinRemap can record what you do and play it back. Nothing happens until you name them.

[macro]
record_start = "S-F10"  # press to start recording
# record_stop = "S-F11" # omit it and the start key stops it too
record_play  = "F10"    # press to replay

Press Shift+F10, do the work, press it again, then press F10 as often as you like. While a recording runs, a banner sits at the bottom of whichever display holds the app you are typing into:

Recording macro  3/20   notepad.exe in progress   —   S-F10 to stop, F10 to replay

It follows you as you switch apps and displays, names the app receiving the keystrokes, and repeats the keys that end and replay the recording — so a recording never runs unnoticed, and you never have to open the config file to find out how to stop it. Replay shows the same banner with the commands it is sending.

Worth knowing before you rely on it

• 20 commands per recording. A command is one chord: C-a is one, the two strokes of A-x h are two. The 21st ends the recording and says so; nothing is dropped quietly.
• Nothing is written to disk. The recording lives in memory and is gone when WinRemap exits, and it is never saved to your config file. To keep a sequence, write it as a macro rule instead.
• What is recorded is what WinRemap emitted, not the keys you pressed. With "C-h" = "Back" in effect, the recording holds Back.
• Order, not timing. Each command is tapped once, in order. How long you held a key, and holding one key while pressing another, are not reproduced — Emacs keyboard macros behave the same way.
• One recording is kept; recording again replaces it. The replay key does nothing while a replay is running, and an in-progress recording is dropped if you disable WinRemap or reload the config, since the key that would end it comes from that file.

delay_ms paces a replay exactly as it paces a config macro — see [macro] in the configuration guide.