On 10/16/14, 4:37 PM, Geir Hauge wrote: > Regardless though, shouldn't source <(declare -xp) work whether or not > the environment contains invalid identifiers? It doesn't at present: > > $ env %=% bash -c 'echo "$BASH_VERSION"; source <(declare -xp)' > 4.3.30(1)-release > /dev/fd/63: line 1: declare: `%': not a valid identifier > > Isn't declare -p output meant to be reusable as shell input?
Yeah. Names that get imported from the environment, but which are not valid shell identifiers, should not leak into declare -p output. I made that change about ten days ago, and it will be in the next release of bash. The current warning is an annoyance but otherwise doesn't impact anything. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/