closeOnExit seems not to work reliably on preview #20612

Closed
opened 2026-01-31 07:19:02 +00:00 by claunia · 3 comments
Owner

Originally created by @dovholuknf on GitHub (Oct 2, 2023).

Windows Terminal version

1.19.2682.0

Windows build number

10.0.22621.2283

Other Software

Ubuntu-22 WSL

Steps to reproduce

I wish I could figure it out. I've been doing everything I always do, I have closeOnExit on but I'm routinely seeing the "process exited with code 130 windows terminal press ctrl-d" message

Expected Behavior

I expect the terminal to 'just close'

Actual Behavior

terminal doesn't actually close and i see: "process exited with code 130 windows terminal"

Originally created by @dovholuknf on GitHub (Oct 2, 2023). ### Windows Terminal version 1.19.2682.0 ### Windows build number 10.0.22621.2283 ### Other Software Ubuntu-22 WSL ### Steps to reproduce I wish I could figure it out. I've been doing everything I always do, I have closeOnExit on but I'm routinely seeing the "process exited with code 130 windows terminal press ctrl-d" message ### Expected Behavior I expect the terminal to 'just close' ### Actual Behavior terminal doesn't actually close and i see: "process exited with code 130 windows terminal"
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:19:03 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Oct 2, 2023):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #16068 for more discussion.

/dup #16068

@zadjii-msft commented on GitHub (Oct 2, 2023): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #16068 for more discussion. /dup #16068
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Oct 2, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 2, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Author
Owner

@dovholuknf commented on GitHub (Oct 2, 2023):

Thanks. I did try to look for a duplicate before filing it and I can see why I didn't find it after reading that issue :)

@dovholuknf commented on GitHub (Oct 2, 2023): Thanks. I __did__ try to look for a duplicate before filing it and I can see why I didn't find it after reading that issue :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20612