[Bug] Code Runner-created terminal is not reused after a terminal in VSCode is closed about vscode-code-runner

[the-chenergy]

I think the fix should be around here:

vscode-code-runner/src/extension.ts

Lines 9 to 11 in 97af108

	vscode.window.onDidCloseTerminal(() => {
	codeManager.onDidCloseTerminal();
	});

VSCode's API function onDidCloseTerminal seems to have one argument in the callback, the terminal being closed. I found an example usage of onDidCloseTerminal here in VSCode's tests.

So perhaps we can just check if the terminal that's closing matches the one recorded in CodeManager._terminal before setting that to null:

vscode-code-runner/src/codeManager.ts

Lines 35 to 37 in 97af108

	public onDidCloseTerminal(): void {
	this._terminal = null;
	}

[HoseynAAmiri]

I just installed it and saw a similar effect. If you mess around with the terminals, it will add another one. If you have nothing, then run it via code runner, it keeps using it. I think it is like it remembers the index of the terminal and if it couldn't find it, it will create a new one even though the previously made terminal is somewhere there. It would be nice if it could remember its one and only generated terminal, or use the existing one that is most likely the relevant one to its own.