Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15167 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-14 16:40 -0400 |
| Last post | 2019-07-14 16:40 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Job-control not fully working in subshells since v4.4 ? Chet Ramey <chet.ramey@case.edu> - 2019-07-14 16:40 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-14 16:40 -0400 |
| Subject | Re: Job-control not fully working in subshells since v4.4 ? |
| Message-ID | <mailman.1331.1563136830.2688.bug-bash@gnu.org> |
On 7/12/19 3:06 PM, Luca Landi wrote: > Bash Version: 5.0 > Patch Level: 7 > Release Status: release > > Description: > > It appears that, since ca. v4.4, job-control from within an interactive subshell > is still allowed but does not work fully because the shell won't hand over > foreground-ness. Bash-4.4 is where the shell started to care about whether or not it was running in the background for the purposes of giving away the terminal to different process groups. Your example is a case where the shell doesn't note the right value for the shell's own process group. Adding that seems to fix the problem. Chet -- ``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/
Back to top | Article view | gnu.bash.bug
csiph-web