{"version":"2.1.221","anchor":"keybinding-config-errors-always-report-as-parse-errors","canonical_anchor":"keybinding-config-errors-always-report-as-parse-errors","heading":"Keybinding config errors always report as parse errors","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/keybinding-config-errors-always-report-as-parse-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Keybinding config errors always report as parse errors\n\nBroken keybinding config now always reports an error instead of silently reverting to defaults.\n\n**What**\n\nA failure loading your keybinding config is now always logged, instead of some failures silently falling back to defaults.\n\n**Details**\n\n- removed the special case that treated an abort or ENOENT-style error as a clean load returning the default bindings\n- every caught error now logs and records `keybinding_config_parse_error`\n\n**Evidence**\n\n`keybinding_config_parse_error`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}