Can we get a one_shot option at the key level?

[louis-vinchon]

Is your feature request related to a problem? Please describe.
I want to be able to keep a table "open" just like we can currently do with the one_shot option of wezterm.action.ActivateKeyTable, but at the key level.

Currently, if I want a given key to not close the table, I have to make the entire table one_shot, or move that key to its own table, which is unwieldy.

Describe the solution you'd like
Ideally something like this:

config.keys = {
    { key = 'a', action = action.ActivateLastTab, one_shot = false },
}
-- or
config.keys = {
    { key = 'a', action = action.ActivateLastTab, opts = { one_shot = false } },
}

That would be way more flexible.

Describe alternatives you've considered
I considered moving the key to its own table, but as far as I can tell, that would mean lengthening my key sequence by one more character, which is inconvenient and less ergonomic. And it also adds a lot of boilerplate code.

Additional context
~

[bew]

There is no automatic way to do that no.

But for a single key you could explicitly call PopKeyTable action after the wanted action to simulate the one-shot behavior
Something like this:

...
{ key = "a", action = act.Multiple { act.ActivateLastTab, act.PopKeyTable } }
...

[louis-vinchon]

I see, so I could make a table one_shot = false, but then for each individual key that DO need to be one_shot, do what you suggested to explicitly trigger the one_shot anyway.

It's still a lot of code for what it does.

[bew]

Yes, keep in mind you are in a Lua interpreter, you can always write functions to simplify recurring patterns in your config ;)

[louis-vinchon]

How would that work for the "root table" config.keys? As far as I know I can't make it one_shot = false.

[bew]

I'm not sure what behavior you want with the root table, as those keys are always available anyway 🤔

[louis-vinchon]

Yeees, I am getting mixed up with another (technically unrelated) issue I have that also impacts the "openess" of tables.

If I have mods = 'CTRL', keys = 'h,j,k,l' mappings in the root table. I can press CTRL and then h, then j, then k ... without letting go of CTRL and it will work. But I cannot do that with mods = LEADER, I can do Leader then h, then I need to let go of LEADER and then press it again with j. Basically start from scratch, which to me feels like a closed table, without actually, technically being closed. It's due to the LEADER key press being dropped after the next keystroke.

That's the scenario I was thinking of.

[bew]

For anything slightly more complex that the default LEADER system (which predates the Key Tables system), I'd highly suggest you to make your own leader Key Table, and then use the flexibility of ActivateKeyTable to enable one shot mode as needed.

[louis-vinchon]

That's the direction I am currently working towards I think?

config.keys = {
    {
        key = 'VoidSymbol',
        action = action.ActivateKeyTable({ name = 'config_keys', one_shot = false }),
    }
}

And then cram everything in the config_keys table.

For the one_shot mappings, I think they'll be the exception rather than the norm, so making an action wrapper with action.Multiple and action.ClearKeyTableStack shouldn't be to bad.