You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, keybindings in OpenCode, such as Ctrl+K for the command dialog, are hardcoded. This can lead to conflicts with keybindings in other tools commonly used in the terminal, like tmux.
For example, many tmux users have Ctrl+K bound for pane navigation. This conflict prevents the OpenCode command dialog from being accessible when running OpenCode inside tmux.
It would be beneficial to allow users to configure keybindings through the .opencode.json configuration file to resolve such conflicts and allow for greater personalization.
Suggested approach: Add a section in the .opencode.json file where users can specify custom keybindings for various actions.
The text was updated successfully, but these errors were encountered:
There is a PR #136 for that, @jesses-code-adventures started it and I have a few change requests, If @jesses-code-adventures pushes the changes before next week I'll get it merge, if not I can continue with it next week.
Currently, keybindings in OpenCode, such as
Ctrl+K
for the command dialog, are hardcoded. This can lead to conflicts with keybindings in other tools commonly used in the terminal, like tmux.For example, many tmux users have
Ctrl+K
bound for pane navigation. This conflict prevents the OpenCode command dialog from being accessible when running OpenCode inside tmux.It would be beneficial to allow users to configure keybindings through the
.opencode.json
configuration file to resolve such conflicts and allow for greater personalization.Suggested approach: Add a section in the
.opencode.json
file where users can specify custom keybindings for various actions.The text was updated successfully, but these errors were encountered: