terminal restart for integrated pwsh can cause cursor to go to wrong location

[amunger]

I had a terminal restart occur for some reason, and from there, the cursor went to the wrong location and was not working well.
Resizing/minimizing the window did not help.
had "terminal.integrated.windowsUseConptyDll": true,
running clear made the issue go away.

[amunger]

related to #241978

[Tyriar]

Probably need to do:

vscode/src/vs/platform/terminal/node/ptyService.ts

Lines 267 to 279 in 3ac9e26

	// Conpty v1.22+ uses passthrough and doesn't reprint the buffer often, this means that when
	// the terminal is revived, the cursor would be at the bottom of the buffer then when
	// PSReadLine requests `GetConsoleCursorInfo` it will be handled by conpty itself by design.
	// This causes the cursor to move to the top into the replayed terminal contents. To avoid
	// this, the post restore message will print new lines to get a clear viewport and put the
	// cursor back at to top left.
	let postRestoreMessage = '';
	if (isWindows) {
	const lastReplayEvent = terminal.replayEvent.events.length > 0 ? terminal.replayEvent.events.at(-1) : undefined;
	if (lastReplayEvent) {
	postRestoreMessage += '\r\n'.repeat(lastReplayEvent.rows - 1) + `\x1b[H`;
	}
	}

Here too:

vscode/src/vs/workbench/contrib/terminal/browser/terminalProcessManager.ts

Lines 568 to 572 in 3ac9e26

	// For normal terminals write a message indicating what happened and relaunch
	// using the previous shellLaunchConfig
	const message = localize('ptyHostRelaunch', "Restarting the terminal because the connection to the shell process was lost...");
	this._onProcessData.fire({ data: formatMessageForTerminal(message, { loudFormatting: true }), trackCommit: false });
	await this.relaunch(this._shellLaunchConfig, this._dimensions.cols, this._dimensions.rows, false);

[vs-code-engineering]

Sharing media from merged PR #307212 for verification:

ptyRestartFix.mp4

Source PR: #307212