|
From: | Chet Ramey |
Subject: | Re: jobs built-in command and PROMPT_COMMAND |
Date: | Fri, 1 Oct 2021 10:39:41 -0400 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 |
On 10/1/21 10:30 AM, Jesse Hathaway wrote:
On Fri, Oct 1, 2021 at 8:22 AM Greg Wooledge <greg@wooledge.org> wrote:I think you're looking for this: checkjobs If set, bash lists the status of any stopped and running jobs before exiting an interactive shell. If any jobs are running, this causes the exit to be deferred until a second exit is attempted without an intervening command (see JOB CONTROL above). The shell always postpones ex‐ iting if any jobs are stopped.This doesn't seem to work for me, what am I doing wrong?
Running `jobs' immediately before exiting cancels the check. You know there are jobs running: you just saw them. If that was important, you presumably would not have tried to exit. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
[Prev in Thread] | Current Thread | [Next in Thread] |