From 291d77e38d7620ea20b717e60af0bdc74b8bd3de Mon Sep 17 00:00:00 2001
From: sezanzeb <proxima@hip70890b.de>
Date: Sat, 19 Dec 2020 23:01:36 +0100
Subject: [PATCH] update usage.md

---
 readme/usage.md | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/readme/usage.md b/readme/usage.md
index 2b354212..b08d1907 100644
--- a/readme/usage.md
+++ b/readme/usage.md
@@ -67,11 +67,14 @@ Wayland than with X11 for me.
 ## Configuration Files
 
 The default configuration is stored at `~/.config/key-mapper/config.json`.
-The current default configuration as of commit `42cb7fe` looks like:
+The current default configuration as of commit `42cb7fe` looks like, with
+an example autoload entry:
 
 ```json
 {
-    "autoload": {},
+    "autoload": {
+        "Logitech USB Keyboard": "preset name"
+    },
     "macros": {
         "keystroke_sleep_ms": 10
     },
@@ -86,6 +89,9 @@ The current default configuration as of commit `42cb7fe` looks like:
 }
 ```
 
+`preset name` refers to `~/.config/key-mapper/device name/preset name.json`.
+The device name can be found with `evtest`.
+
 Anything that is relevant to presets can be overwritten in them as well.
 Here is an example configuration for preset "a" for the "gamepad" device:
 `~/.config/key-mapper/gamepad/a.json`
@@ -110,4 +116,5 @@ it inherits all configurations from `~/.config/key-mapper/config.json`.
 If config.json is missing some stuff, it will query the hardcoded default
 values.
 
-The event codes can be read using `evtest`.
+The event codes can be read using `evtest`. Available names in the mapping
+can be listed with `key-mapper-service --key-names`.