Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16381 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2020-06-15 09:30 -0400 |
| Last post | 2020-06-15 09:30 -0400 |
| 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: Changes to HISTIGNORE are not honored when changed via a reference? Chet Ramey <chet.ramey@case.edu> - 2020-06-15 09:30 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2020-06-15 09:30 -0400 |
| Subject | Re: Changes to HISTIGNORE are not honored when changed via a reference? |
| Message-ID | <mailman.1926.1592227847.2541.bug-bash@gnu.org> |
On 6/13/20 6:17 PM, James D. Lin wrote: > Bash Version: 5.0 > Patch Level: 3 > Release Status: release > > Description: > If I modify the `HISTIGNORE` variable indirectly through a reference (e.g. > via `declare -n` or `local -n`), `HISTIGNORE` reflects the change, but the > change isn't honored. Thanks for the report. Bash checks whether `historyref' is the special variable with side effects, not the target of the nameref. 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