Re: Changes to HISTIGNORE are not honored when changed via a reference?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Changes to HISTIGNORE are not honored when changed via a reference?
Date	2020-06-15 09:30 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.1926.1592227847.2541.bug-bash@gnu.org> (permalink)
References	<CADPatTfW9=Hh2kuDXjs7L3XByUgS+zqUq=c62J583J0SOWO0Mw@mail.gmail.com> <d8cb49a2-761e-e528-e716-023ffba6e5dd@case.edu>

Show all headers | View raw

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 gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Changes to HISTIGNORE are not honored when changed via a reference? Chet Ramey <chet.ramey@case.edu> - 2020-06-15 09:30 -0400

csiph-web