Is it possible to "derive" my keybindings from e.g., flow.json and override only some key bindings?

[nurpax]

When modifying keybindings, I'd like to f.ex. completely disable all the smart_insert_pair bindings. I just prefer to type double quotes/apostrophes/etc myself. It goes against grain esp. when writing just plain English text with apostrophes.

So far I've simply taken the keys/flow.json file and deleted the smart_insert_pair rows. But it'd be nice to be able to use the defaults for everything, and only selectively turn some of these things off:

https://codeberg.org/neurocyte/flow/src/commit/fa71704a9471c05d8c9b50a04eff6a9e170313bd/src/keybind/builtin/flow.json#L232

[neurocyte]

Yes, it is possible to derive keybindings from the default flow bindings. In fact, any keybinding section that does not have an explicit "inherit" field automatically derives from the flow mode section with the same name.

So to just disable smart_insert_pair you can use this simple keybindings config:

{
    "normal": {
        "press": [
            ["\"", "insert_chars", "\""],
            ["'", "insert_chars", "'"],
            ["`", "insert_chars", "`"],
            ["(", "insert_chars", "("],
            [")", "insert_chars", ")"],
            ["[", "insert_chars", "["],
            ["]", "insert_chars", "]"],
            ["{", "insert_chars", "{"],
            ["}", "insert_chars", "}"],
            ["‘", "insert_chars", "‘"],
            ["’", "insert_chars", "’"],
            ["“", "insert_chars", "“"],
            ["”", "insert_chars", "”"],
            ["‚", "insert_chars", "‚"],
            ["‘", "insert_chars", "‘"],
            ["«", "insert_chars", "«"],
            ["»", "insert_chars", "»"],
            ["¿", "insert_chars", "¿"],
            ["¡", "insert_chars", "¡"]
        ]
    }
}

Don't save this as flow.json though. Use a different name, otherwise there will be nothing to inherit from and you'll have no keybinds at all!

[neurocyte]

Here is a slightly more complete version:

{
    "normal": {
        "press": [
            ["\"", "insert_chars", "\""],
            ["'", "insert_chars", "'"],
            ["`", "insert_chars", "`"],
            ["(", "insert_chars", "("],
            [")", "insert_chars", ")"],
            ["[", "insert_chars", "["],
            ["]", "insert_chars", "]"],
            ["{", "insert_chars", "{"],
            ["}", "insert_chars", "}"],
            ["‘", "insert_chars", "‘"],
            ["’", "insert_chars", "’"],
            ["“", "insert_chars", "“"],
            ["”", "insert_chars", "”"],
            ["‚", "insert_chars", "‚"],
            ["‘", "insert_chars", "‘"],
            ["«", "insert_chars", "«"],
            ["»", "insert_chars", "»"],
            ["¿", "insert_chars", "¿"],
            ["¡", "insert_chars", "¡"]
        ]
    },
    "home": {
        "on_match_failure": "ignore",
        "press": []
    }
}

The added empty "home" section allows the home screen to correctly display the mode name. Without it, it just displays flow because that is where the entire "home" keybind submode comes from.

I call this mode flow-nsp.json for "no smart pairs".