A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1879 ====================================================================== Reported By: calestyo Assigned To: ====================================================================== Project: 1003.1(2024)/Issue8 Issue ID: 1879 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section: Shell Command Language Page Number: various Line Number: various Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2024-11-26 04:30 UTC Last Modified: 2024-11-27 07:19 UTC ====================================================================== Summary: claifications/improvements around command/exec and special built-in redirection errors ======================================================================
---------------------------------------------------------------------- (0006972) larryv (reporter) - 2024-11-27 07:19 https://austingroupbugs.net/view.php?id=1879#c6972 ---------------------------------------------------------------------- https://austingroupbugs.net/view.php?id=1879#c6971:<blockquote>Admittedly, it's still no perfect. But I thought the "WITH the consequences" would make it a bit clearer, that these actually follow from the 1-125 exit status. The original text just says "see..." but that is IMO less strong. Anyway... I'm open for better wordings, perhaps one should use one that makes also clear that the consequences happen *immediately* after the `exec` "returns"?</blockquote>Given that https://austingroupbugs.net/view.php?id=1157 added the following text to the DESCRIPTION section...<blockquote>If the <i>exec</i> command fails, a non-interactive shell shall exit from the current shell execution environment; [UP] [Option Start] an interactive shell may exit from a subshell environment but shall not exit if the current shell environment is not a subshell environment. If the <i>exec</i> command fails and the shell does not exit, any redirections associated with the <i>exec</i> command that were successfully made shall take effect in the current shell execution environment. [Option End]</blockquote>...it seems to me that the lack of descriptions of consequences of errors in the EXIT STATUS section is intentional. Issue History Date Modified Username Field Change ====================================================================== 2024-11-26 04:30 calestyo New Issue 2024-11-26 04:30 calestyo Name => Christoph Anton Mitterer 2024-11-26 04:30 calestyo Section => Shell Command Language 2024-11-26 04:30 calestyo Page Number => various 2024-11-26 04:30 calestyo Line Number => various 2024-11-26 08:23 larryv Note Added: 0006970 2024-11-26 08:26 larryv Note Edited: 0006970 2024-11-26 08:27 larryv Note Edited: 0006970 2024-11-26 18:48 calestyo Note Added: 0006971 2024-11-27 07:19 larryv Note Added: 0006972 ======================================================================
