Skip to content
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

Open
30 of 45 tasks
vparfonov opened this issue Jan 14, 2019 · 13 comments
Open
30 of 45 tasks

[plug-in] Implement VS Code Built-in Commands #4050

vparfonov opened this issue Jan 14, 2019 · 13 comments
Labels
commands issues related to application commands epic epic issues consisting of multiple smaller issues plug-in system issues related to the plug-in system Team: Che-Editors issues regarding the che-editors team vscode issues related to VSCode compatibility

Comments

@vparfonov
Copy link
Contributor

vparfonov commented Jan 14, 2019

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:

@vparfonov vparfonov added epic epic issues consisting of multiple smaller issues plug-in system issues related to the plug-in system labels Jan 14, 2019
@akosyakov
Copy link
Member

vscode.executeDocumentSymbolProvider -> #4048

@akosyakov
Copy link
Member

akosyakov commented Jan 17, 2019

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.

@tsmaeder
Copy link
Contributor

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

@benoitf
Copy link
Contributor

benoitf commented Jan 29, 2019

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 vscode.)

here is another list as well:
https://code.visualstudio.com/docs/getstarted/keybindings#_navigation

so I would suppose vscode. commands should go as @tsmaeder said but for the others it should either rename original name (breaking change..) or currently add the alias but in theia command contribution, not only in vscode.

@akosyakov
Copy link
Member

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 vscode.)

please see #4193 (comment)

cc @svenefftinge

@akosyakov
Copy link
Member

akosyakov commented Jan 31, 2019

here is another list as well:
https://code.visualstudio.com/docs/getstarted/keybindings#_navigation

👍

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

@vinokurig
Copy link
Contributor

vinokurig commented Nov 26, 2019

It would be great to have next commands that are needed for the VsCode Emacs Keymap extension:

  • lineBreakInsert - Insert Enter
  • workbench.action.openRecent - Open recent command #7812
  • workbench.action.splitEditorDown - Split editor horizontal
  • workbench.action.splitEditorRight - Split editor vertical
  • workbench.action.toggleEditorGroupLayout - Toggle split layout (vertical to horizontal)
  • workbench.action.navigateEditorGroups - Focus other split editor
  • workbench.action.toggleSidebarVisibility - Toggle sidebar visibility
  • workbench.action.toggleZenMode - Toggle Zen mode

see #6625

@vinokurig
Copy link
Contributor

  • editor.action.reindentselectedlines

Needed for the VsCode Vim extension see: #6687

@tomer-epstein
Copy link
Contributor

tomer-epstein commented Dec 29, 2019

Is there a plan to imlement 'vscode.openFolder' soon?

  • vscode.openFolder - Open a folder or workspace in the current window or new window depending on the newWindow argument.

@akosyakov
Copy link
Member

@tomer-epstein PRs are welcomed, it should not be hard to implement, there is WorkspaceService .open API which accepts an URI of a folder to open and a second options with an argument whether a window should be preserved. One has to add a new command in PluginVscodeCommandsContribution.

@akosyakov akosyakov added the commands issues related to application commands label Mar 18, 2020
@tavoda
Copy link

tavoda commented Apr 11, 2020

After installing VSCode VIM plugin from https://marketplace.visualstudio.com/items?itemName=vscodevim.vim, I'm getting following error after pressing CTRL+F:

TaskQueue: Error running task. Failed to handle key=. Command with id 'editorScroll' is not registered.. for VSCode VIM extension

Is editorScroll still not implemented?

@akosyakov
Copy link
Member

@tavoda It should be, we receive directly from Monaco editor. Do you use master? It would be worth to file a separate issue.

@akosyakov
Copy link
Member

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.

@azatsarynnyy azatsarynnyy added the Team: Che-Editors issues regarding the che-editors team label May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
commands issues related to application commands epic epic issues consisting of multiple smaller issues plug-in system issues related to the plug-in system Team: Che-Editors issues regarding the che-editors team vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

8 participants