-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[plug-in] Implement VS Code Built-in Commands #4050
Comments
|
Whoever will do it, please check how each command is implemented in VS Code. Sometimes it is just calling another command which can be already available via Monaco. In this case we don't need to expose any internal Monaco API or copy code from VS Code, but just use our command registry and execute the very same command. |
I guess the commands should be registered here: https://github.com/theia-ide/theia/blob/master/packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts#L35 |
I'm not finding anymore the issue but I'm pretty sure to have read that @svenefftinge wanted to align all the names of commands to match VS Code one (I suppose all the names that are not prefixed by here is another list as well: so I would suppose |
please see #4193 (comment) |
👍 maybe we keep this issue as an epic and open issues per a shortcut group to implement them separately and track progress? for the debug group: #4204 |
It would be great to have next commands that are needed for the VsCode Emacs Keymap extension:
see #6625 |
Needed for the VsCode Vim extension see: #6687 |
Is there a plan to imlement 'vscode.openFolder' soon?
|
@tomer-epstein PRs are welcomed, it should not be hard to implement, there is |
After installing VSCode VIM plugin from https://marketplace.visualstudio.com/items?itemName=vscodevim.vim, I'm getting following error after pressing CTRL+F:
Is editorScroll still not implemented? |
@tavoda It should be, we receive directly from Monaco editor. Do you use master? It would be worth to file a separate issue. |
Let's keep this issue as a live document to track missed commands coverage. One can file individual issues as well, but please update the first comment of this issue. |
Built-in Commands used in VS Code Extensions widely, so for beeter support in as Theia Plugin we need to cover such command as is it possible.
List of command described here:
https://code.visualstudio.com/api/references/commands
Issues:
vscode.executeDocumentSymbolProvider
command foremmet
VS Code extension #4048The text was updated successfully, but these errors were encountered: