You'll notice
Useful3 Signal2
Aborting a command that should move to the background now leaves the shell running.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a command is aborted for a reason that is supposed to move the shell into the background, the process is now left running instead of being killed.
Details
- A shared check decides, from the abort reason and the kind of caller, whether the shell should be backgrounded; the caller kind defaults to the inner shell.
- The same check gates two other places that stop shells.
Evidence
backgroundsTheShell
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Custom keybinding actions now use a
command:prefix instead ofx-Both mention command
-
v2.1.242
Background shells that are still working are no longer killed during cleanup
Both mention shell
-
v2.1.248
Background shell results arrive as a tool result, not a fake user message
Both mention shell