{"version":"2.1.247","anchor":"aborting-no-longer-kills-shells-that-were-meant-to-keep-runn","canonical_anchor":"aborting-no-longer-kills-shells-that-were-meant-to-keep-runn","heading":"Aborting no longer kills shells that were meant to keep running","tier":"notice","area":"Shell Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/aborting-no-longer-kills-shells-that-were-meant-to-keep-runn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Aborting no longer kills shells that were meant to keep running\n\nAborting a command that should move to the background now leaves the shell running.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- 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.\n- The same check gates two other places that stop shells.\n\n**Evidence**\n\n`backgroundsTheShell`\n\n- Area: Shell Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}