-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
bugSomething isn't workingSomething isn't workingfeature requestFeature request, not a bugFeature request, not a bug
Description
App Version
Version: 3.13.2
API Provider
OpenRouter
Model Used
not model related
Actual vs. Expected Behavior
for us vim-key fanatics, it would be extremely helpful if roo-code would set a unique context if the input field is focused, so that we can restrict defined keybindings not to be triggered when in roo-code
for example:
// toggle sidebar (explorer)
{
"key": "space e",
"command": "runCommands",
"args": {
"commands": [
"workbench.action.toggleSidebarVisibility",
"workbench.files.action.focusFilesExplorer"
]
},
"when": "vim.mode == 'Normal' && (editorTextFocus || !inputFocus) && !sideBarFocus"
},
{
"key": "space e",
"command": "runCommands",
"args": {
"commands": [
"workbench.action.toggleSidebarVisibility",
"workbench.action.focusActiveEditorGroup"
]
},
"when": "sideBarFocus && !inputFocus"
},
{
"key": "space e",
"when": "vim.mode == 'Normal' && editorTextFocus && foldersViewVisible",
"command": "workbench.action.toggleSidebarVisibility"
},
this works fine, but there is no clean way to exclude the webview to be excluded (!webviewFocus is not doing the trick)
if roo-code would expose it's context when the user focused the input field, this could be easyly excluded within the custom keybindings
Detailed Steps to Reproduce
Relevant API Request Output
Additional Context
No response
dosubot
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingfeature requestFeature request, not a bugFeature request, not a bug