-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
API: No way to find out that an editor has closed #643
Labels
Milestone
Comments
@bpasero I don't see @alexandrudima I think this is a duplicate of the editor change event firing to often |
@jrieken Maybe a new |
jrieken
added a commit
that referenced
this issue
Oct 13, 2016
jrieken
added a commit
that referenced
this issue
Oct 13, 2016
jrieken
added a commit
that referenced
this issue
Oct 13, 2016
fyi @joaomoreno - please give it a try |
Seems to work like a charm. 🎆 |
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For the VS Code API tests I have a clean up function that signals that it is done when all editors are closed. Currently the solution is hacky, it needs to install a setInterval to periodically check on the
vscode.window.visibleTextEditors
property to eventually become 0 (see https://github.com/Microsoft/vscode/blob/master/extensions/vscode-api-tests/src/utils.ts#L52).The issue is that the
window.onDidChangeActiveTextEditor
event is not good enough for testing on the visible text editors as shown by the following test:The value passed in from the event is null as expected because I am running the close all editors action. However,
window.visibleTextEditors.length
is still 1 at that point.The text was updated successfully, but these errors were encountered: