-
Notifications
You must be signed in to change notification settings - Fork 28k
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
Remove Terminal.onDidWriteData #80836
Conversation
Replaced by vscode.window.onDidWriteTerminalData Fixes #78574
this.detectPattern(s); | ||
})); | ||
}); | ||
this.disposables.push(vscode.window.onDidWriteTerminalData(e => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weinand fyi debug-server-ready was on a deprecated API that just got removed, I didn't test this so please review.
@Tyriar the serverReadyAction feature no longer works in the integrated terminal since the package.json is missing a I addition I will have to rewrite the code because the old implementation tried to be very careful to register I'm not sure that the new API is an improvement. It is definitely not performance-wise. /cc @jrieken |
That's on purpose. For once to align with the global event rules and then the VSLS use-case is to listen on all terminal anyways, hence no performance difference. Tho, because we are aware that (global and private events are equally dangerous) we have no plans to ever move that API out of proposed. |
Replaced by vscode.window.onDidWriteTerminalData
Fixes #78574