A NOTE has been added to this issue. ====================================================================== https://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-25 07:34 UTC ====================================================================== Summary: ambiguous description of which attribtes `unset` unsets in case of readonly attribute being set ======================================================================
---------------------------------------------------------------------- (0006679) kre (reporter) - 2024-02-25 07:34 https://austingroupbugs.net/view.php?id=1806#c6679 ---------------------------------------------------------------------- When working out the desired wording to make this clear (and I believe I agree with what is being proposed, but as I said in a note to https://austingroupbugs.net/view.php?id=1075, the text here should not refer to "all attributes" - since everyone agrees that readonly cannot be undone by "unset" - the only attribute that the standard knows about is "export" - the text just need to say that if the variable is not readonly, the export attibute is cleared, as well as the value. What bash chooses to do with its "integer" attribute is none of our business (nor any of its others) - similarly for other shells that have more attributes than readonly and export ... the NetBSD shell has an "unexportable" attribute, that prevents "export" being applied (we have one specific use of that one). With all of this, everyone should also note that being readonly does not (in any shell I can test) prevent the "export" attribute from being set, it just stops "unset" from clearing it. There's no reason a shell that provides some other way (than unset) from removing the export attribute cannot allow that other mechanism to remove "export" from a readonly variable (all of that is beyond the standard however - but the standard must not prohibit any of this.) 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 2024-02-13 22:48 calestyo Note Added: 0006655 2024-02-13 22:55 calestyo Note Added: 0006656 2024-02-25 07:34 kre Note Added: 0006679 ======================================================================
