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-26 18:48 UTC ====================================================================== Summary: claifications/improvements around command/exec and special built-in redirection errors ======================================================================
---------------------------------------------------------------------- (0006971) calestyo (reporter) - 2024-11-26 18:48 https://austingroupbugs.net/view.php?id=1879#c6971 ---------------------------------------------------------------------- > It does in POSIX mode. Yes. I've mentioned that via an example a bit further down in my original text. But at least per default it doesn't do so. > How is this any better than the current text, > which already has that xref? You're just moving > the xref around. . 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"? > What do you mean? The grep command never runs here. > If it does, the error message is printed fine. Ah, of course. Thanks for pointing that out. So then I'd guess - if it was agreed that such an example was a worthy addition to the standard - one should use: ( { command exec <any-redirections> || exit <some-exit-status-not-used-by-utility>; } 2>/dev/null; <utility> <argument>… ) and perhaps mention that instead of ( ... ) it would of course also work with other subshells ( `$(...)`). Not sure whether one should also mention that it can be done without subshells as well. 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 ======================================================================
