Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #13793 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-03-02 14:49 -0500 |
| Last post | 2018-03-02 14:49 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Unset array doesn't work Chet Ramey <chet.ramey@case.edu> - 2018-03-02 14:49 -0500
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-03-02 14:49 -0500 |
| Subject | Re: Unset array doesn't work |
| Message-ID | <mailman.10033.1520020196.27995.bug-bash@gnu.org> |
On 2/28/18 5:38 PM, Robert Elz wrote: > I would change "appear" to "be" in the description of the current scope > behaviour. Now we're straying into semantics. If the variable were `really' unset, as opposed to just appearing unset, that could be construed as meaning the global instance (or any previous local instances) would be gone, too. I could see pairing it with text that says the variable at the current or nearest previous instance is unset and remains so until that function returns. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web