> we're working on a new terminal sequence specification that would allow terminal programs to expose any of their actions directly in the command palette (e.g. imagine Neovim commands being fully available in the command palette).
Not just macOS: "The command palette is bound by default to ctrl+shift+p on GTK and cmd+shift+p on macOS."
> The command palette exposes almost every available keybind.
> This has some immediate benefits, namely that you can access keybind actions even if they aren't bound to a keybind. This is useful for infrequently used actions. ... For example, I personally find myself using the move_tab action via the command palette frequently, but not frequently enough to justify binding it.
> we're working on a new terminal sequence specification that would allow terminal programs to expose any of their actions directly in the command palette (e.g. imagine Neovim commands being fully available in the command palette).
/mic-drop
Not just macOS: "The command palette is bound by default to ctrl+shift+p on GTK and cmd+shift+p on macOS."
> The command palette exposes almost every available keybind.
> This has some immediate benefits, namely that you can access keybind actions even if they aren't bound to a keybind. This is useful for infrequently used actions. ... For example, I personally find myself using the move_tab action via the command palette frequently, but not frequently enough to justify binding it.