eclipse-che
Automatical mapping keybindings.json
Summary
Hi team,
I have the task to automatically map custom keybindings.json on checode loading. I tried to put the file into ~/.config/Code/User or other default paths for vscode, but checode didn't load it. I found and configured embedded keybindings.json via checode comand line ( Open Keyboard Shortcuts (JSON)), it opens the keybindings.json file which can be edited and applied, but I couldn't find its location on the FS. I tried to grep text and find by the name, but unsuccessfully :( When I selected to copy path of the file it returned me (Settings): /User/keybinding.json. Could you please tell me where this file located? may be it is stored in the internal storage?
Thanks in advance!
Relevant information
No response
The use case: we want to have reproducible dev environments (including the settings, extensions and the key bindings). That seems possible with settings and extensions (through workspace settings.json and extensions.json), but we couldn't do it it for keybindings.json.
When I selected to copy path of the file it returned me (Settings): /User/keybinding.json.
IIRC, files stored under /User/ are stored in the browser's local storage.
This may be achievable somehow through a patch to CheCode, but I'm not sure how feasible it is. @azatsarynnyy @vitaliy-guliy and @RomanNikitenko would have a better idea.
From the looks of https://github.com/Microsoft/vscode/issues/4504 & https://github.com/Microsoft/vscode/issues/23757, this is not supported in upstream VSCode either (seemingly by design).
I did find a hacky workaround that may be worth a try, but this seems less than ideal and would be unsupported.
CC: @azatsarynnyy @vitaliy-guliy and @RomanNikitenko please take a look :)
IIRC, files stored under /User/ are stored in the browser's local storage.
@AObuchow is correct. Such files are stored in browser's Indexed DB.
AFAIK, @vitaliy-guliy is working on making those configs stored in a file on FS.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
