Skip to content

Conversation

@SalerSimo
Copy link
Contributor

Fix #280043

Now historyService.recentlyClosedEditors will not track terminal editors.

@vs-code-engineering
Copy link

vs-code-engineering bot commented Dec 8, 2025

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@bpasero

Matched files:

  • src/vs/workbench/common/editor/editorInput.ts
  • src/vs/workbench/services/history/browser/historyService.ts

Copy link
Member

@bpasero bpasero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I think this can go in.

Usually even a terminal editor should be supporting re-open, I am not sure why it would not.

@bpasero bpasero added this to the December / January 2026 milestone Dec 10, 2025
@bpasero bpasero enabled auto-merge (squash) December 10, 2025 08:34
@SalerSimo
Copy link
Contributor Author

I investigated further, and the problem is this line: when creating a new editor from a resource that isn’t linked to any active terminal instance, it throws a timeout error.

const attachPersistentProcess = await primaryBackend.requestDetachInstance(terminalIdentifier.workspaceId, terminalIdentifier.instanceId);

@bpasero bpasero merged commit dc4ab7e into microsoft:main Dec 10, 2025
17 checks passed
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.

reopenClosedEditor histories are broke by EditorTerminals.

4 participants