A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1966 ====================================================================== Reported By: stephane Assigned To: ====================================================================== Project: 1003.1(2024)/Issue8 Issue ID: 1966 Category: Shell and Utilities Type: Clarification Requested Severity: Objection Priority: normal Status: New Name: Stephane Chazelas Organization: User Reference: Section: current/previous job in basedefs, jobs, fg, bg utilities Page Number: (page or range of pages) Line Number: (Line or range of lines) Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2025-12-21 11:17 UTC Last Modified: 2026-02-05 17:20 UTC ====================================================================== Summary: Current/previous job definition scattered and ambiguous ======================================================================
---------------------------------------------------------------------- (0007371) geoffclare (manager) - 2026-02-05 17:20 https://www.austingroupbugs.net/view.php?id=1966#c7371 ---------------------------------------------------------------------- Interpretation response ------------------------ The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: ------------- There is a conflict between the description of <current> in the STDOUT section of the jobs utility and the description of the job_id operand for the fg and bg utilities. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- On page 2666 line 87729 section bg, change: <blockquote>If no <i>job_id</i> operand is given, the most recently suspended job shall be used.</blockquote> to: <blockquote>If no <i>job_id</i> operand is given, the <i>job_id</i> for the job that was most recently suspended, placed in the background, or run as a background job shall be used, except that if there is any suspended job: <ul> <li>If the most recently suspended job is still in a suspended state and no other job was started since it was last suspended, that job shall be used.</li> <li>Otherwise, it is unspecified which job shall be used.</li> </ul></blockquote> On page 2928 line 97725 section fg, change: <blockquote>If no <i>job_id</i> operand is given, the <i>job_id</i> for the job that was most recently suspended, placed in the background, or run as a background job shall be used.</blockquote> to: <blockquote>If no <i>job_id</i> operand is given, the <i>job_id</i> for the job that was most recently suspended, placed in the background, or run as a background job shall be used, except that if there is any suspended job: <ul> <li>If the most recently suspended job is still in a suspended state and no other job was started since it was last suspended, that job shall be used.</li> <li>Otherwise, it is unspecified which job shall be used.</li> </ul></blockquote> On page 3022 line 101144 section jobs, delete: <blockquote>If there is any suspended job, then the current job shall be a suspended job. If there are at least two suspended jobs, then the previous job also shall be a suspended job.</blockquote> Issue History Date Modified Username Field Change ====================================================================== 2025-12-21 11:17 stephane New Issue 2026-01-06 10:04 geoffclare Project 1003.1(2013)/Issue7+TC1 => 1003.1(2024)/Issue8 2026-02-05 17:20 geoffclare Note Added: 0007371 ======================================================================
