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

await openEditorAtIndex1 command #2442

Conversation

arussellk
Copy link
Contributor

Previously there was a bug in VSCode which prevented me from doing:

await
vscode.commands.executeCommand('workbench.action.openEditorAtIndex1')

The most recent release of VSCode (1.21.0) fixes the bug. See
microsoft/vscode#44636

What this PR does / why we need it:
This PR ties up a loose end because the latest VSCode release fixed a bug.

Which issue(s) this PR fixes
No specific issue though I mentioned this in #2400 (comment)

Special notes for your reviewer:
This change will impact users who use :tabn or :tabfirst but do not have the latest version of VSCode. For such users, :tabn or :tabfirst will cause the command line (:) to be disabled until VSCodeVim is restarted. What is VSCodeVim's policy on breaking changes (albeit limited) like this?

Previously there was a bug in VSCode which prevented me from doing:
```
await
vscode.commands.executeCommand('workbench.action.openEditorAtIndex1')
```

The most recent release of VSCode (1.21.0) fixes the bug. See
microsoft/vscode#44636
@jpoon
Copy link
Member

jpoon commented Mar 12, 2018

Awesome. Thanks for the follow-up @arussellk.

@jpoon jpoon merged commit fb0e1e8 into VSCodeVim:master Mar 12, 2018
@arussellk arussellk deleted the fix/await-workbench-action-openEditorAtIndex1 branch March 12, 2018 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants