A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1806 ====================================================================== Reported By: calestyo Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1806 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: 2571 Line Number: 83916, ff. Final Accepted Text: ====================================================================== Date Submitted: 2024-02-02 22:53 UTC Last Modified: 2024-02-13 20:25 UTC ====================================================================== Summary: ambiguous description of which attribtes `unset` unsets in case of readonly attribute being set ======================================================================
---------------------------------------------------------------------- (0006654) mirabilos (reporter) - 2024-02-13 20:25 https://www.austingroupbugs.net/view.php?id=1806#c6654 ---------------------------------------------------------------------- How about something like this (I *think* there are no possible other causes of “could not be unset” than it being readonly any more): ──────────────────────────────────────────────────────────────────────── Each variable or function specified by name that does not have the readonly attribute (see Section 2.15 export and readonly) shall be unset and have all of its attributes removed. If -v is specified, name refers to a variable name and the shell shall unset it and remove it from the environment. If -f is specified, name refers to a function and the shell shall unset the function definition. If neither -f nor -v is specified, name refers to a variable; if a variable by that name does not exist, it is unspecified whether a function by that name, if any, shall be unset. Unsetting a variable or function that was not previously set shall not be considered an error and does not cause the shell to abort. […] EXIT STATUS 0 All name operands were successfully unset or not set. >0 At least one name was readonly and could not be unset. Issue History Date Modified Username Field Change ====================================================================== 2024-02-02 22:53 calestyo New Issue 2024-02-02 22:53 calestyo Name => Christoph Anton Mitterer 2024-02-02 22:53 calestyo Section => Shell Command Language 2024-02-02 22:53 calestyo Page Number => 2571 2024-02-02 22:53 calestyo Line Number => 83916, ff. 2024-02-03 00:30 larryv Note Added: 0006647 2024-02-13 20:10 mirabilos Note Added: 0006653 2024-02-13 20:25 mirabilos Note Added: 0006654 ======================================================================
