[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in force_interactive handling

From: Stas Sergeev
Subject: Re: bug in force_interactive handling
Date: Wed, 04 Jan 2012 17:42:09 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

04.01.2012 17:28, Chet Ramey wrote:
Hello Chet, I double-checked that, and with the attached
quick hack I was able to do:
trap bg USR1
and move the job to the background with just that SIGUSR1.
Do you think such a feature is worth being implemented?
I don't think there's enough need to change bg from operating on stopped
jobs to operating on running jobs.  I would not add this to bash.
I didn't mean that at all, and "bg" have almost
nothing to do with the idea.
I just meant for the way to make the trap handler
executed when the foreground job is running.
In my hack it temporary becames the background
job, then the trap is executed. Since the trap executes
"bg", it stays in the background. The command (bg) is
not even needed, maybe it just should be the special
kind of a trap that moves the job to the background
without executing any command? There can be any
kind of an implementation if you think the feature
itself is useful (I think it is, I'll use it :))

reply via email to

[Prev in Thread] Current Thread [Next in Thread]