Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14624
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Special parameter ? |
| Date | 2018-09-21 11:46 -0400 |
| Message-ID | <mailman.1097.1537544817.1284.bug-bash@gnu.org> (permalink) |
| References | <201809211123.w8LBNvHe018414@omac.gsyc.urjc.es> <20180921125705.646znyglxhb6rqga@eeg.ccf.org> <CAMPpeEWtyF=PKPYORSwVAPWVxLj85LDvz=bhth9JUR6q+YuzjQ@mail.gmail.com> <20180921151733.GA31947@ubuntu> |
On 9/21/18 11:17 AM, Eduardo A. Bustamante López wrote: > On Fri, Sep 21, 2018 at 04:17:11PM +0200, Enrique Soriano wrote: >>> You're seeing the status from the creation of the background job (which is >>> always 0), not from its completion. >> >> Ah, I see. >> >> Anyway, the behavior is not coherent with the manual page: in this >> case, $? has the status from the creation of the background job, >> that's not "the status of the most recently executed foreground >> pipeline". > > The thing that creates the background job IS a foreground pipeline. It's a foreground pipeline that creates a background > job, if that makes sense. You're right, but it might be less confusing if I removed the "foreground" from the description. -- ``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 gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Special parameter ? Chet Ramey <chet.ramey@case.edu> - 2018-09-21 11:46 -0400
csiph-web