I think you're asking two different things there.
Is there a way to make bash print this info without the loop?
Yes, but they are not as good as just using the loop.
Is there a cleaner way to get/print only the key=value portion of the output?
Yes, the for
loop. It has the advantages that it doesn't require external programs, is straightforward, and makes it rather easy to control the exact output format without surprises.
Any solution that tries to handle the output of declare -p
(typeset -p
)
has to deal with a) the possibility of the variables themselves containing parenthesis or brackets, b) the quoting that declare -p
has to add to make it's output valid input for the shell.
For example, your expansion b="${a##*(}"
eats some of the values, if any key/value contains an opening parenthesis. This is because you used ##
, which removes the longest prefix. Same for c="${b%% )*}"
. Though you could of course match the boilerplate printed by declare
more exactly, you'd still have a hard time if you didn't want all the quoting it does.
This doesn't look very nice unless you need it.
$ declare -A array=([abc]="'foobar'" [def]='"foo bar"')
$ declare -p array
declare -A array='([def]="\"foo bar\"" [abc]="'\''foobar'\''" )'
With the for
loop, it's easier to choose the output format as you like:
# without quoting
$ for x in "${!array[@]}"; do printf "[%s]=%s\n" "$x" "${array[$x]}" ; done
[def]="foo bar"
[abc]='foobar'
# with quoting
$ for x in "${!array[@]}"; do printf "[%q]=%q\n" "$x" "${array[$x]}" ; done
[def]=\"foo\ bar\"
[abc]=\'foobar\'
From there, it's also simple to change the output format otherwise (remove the brackets around the key, put all key/value pairs on a single line...). If you need quoting for something other than the shell itself, you'll still need to do it by yourself, but at least you have the raw data to work on. (If you have newlines in the keys or values, you are probably going to need some quoting.)
With a current Bash (4.4, I think), you could also use printf "[%s]=%s" "${x@Q}" "${array[$x]@Q}"
instead of printf "%q=%q"
. It produces a somewhat nicer quoted format, but is of course a bit more work to remember to write. (And it quotes the corner case of @
as array key, which %q
doesn't quote.)
If the for loop seems too weary to write, save it a function somewhere (without quoting here):
printarr() { declare -n __p="$1"; for k in "${!__p[@]}"; do printf "%s=%s\n" "$k" "${__p[$k]}" ; done ; }
And then just use that:
$ declare -A a=([a]=123 [b]="foo bar" [c]="(blah)")
$ printarr a
a=123
b=foo bar
c=(blah)
Works with indexed arrays, too:
$ b=(abba acdc)
$ printarr b
0=abba
1=acdc
printf ...%q...
variant is not suitable for reinput to the shell if the array has a@
key as %q doesn't quote it anda=([@]=value)
is a syntax error inbash
. – Stéphane Chazelas May 23 '17 at 07:02"${x@Q}"
quotes that too, since it quotes all strings (and looks nicer). added a note about using that. – ilkkachu May 23 '17 at 07:26zsh
with its variable expansion flags (that again predates bash's by decades and with which you can choose the quoting style: ${(q)var}, ${(qq)var}...) for a better design. bash has the same issue as mksh in that it doesn't quote the empty string (not an issue here as anyway bash doesn't support empty keys). Also, when using quoting styles other than single quote (${var@Q}
resorts to$'...'
for some values) it's important that the code be reinput in the same locale. – Stéphane Chazelas May 23 '17 at 09:20x=; echo "${x@Q}"
does give''
,unset x; echo "${x@Q}"
gives nothing.) Bash's@Q
seems to prefer$'\n'
over a literal newline, which may actually be good in some situations (but I can't tell what others prefer). Of course having a choice there wouldn't be bad. – ilkkachu May 23 '17 at 09:36$'...'
syntax is a potential problem in things likeLC_ALL=zh_HK.big5hkscs bash -c 'a=$'\''\n\u3b1'\''; printf "%s\n" "${a@Q}"'
which outputs$'\n<0xa3><0x5c>'
and0x5c
alone is backslash so you'd have a problem if that quote was interpreted in a different locale. – Stéphane Chazelas May 23 '17 at 10:07