Re: is it a bug that \e's dont get escaped in declare -p output

[Léa Gris]

Le 17/03/2021 à 20:58, Ilkka Virta écrivait :
> On Wed, Mar 17, 2021 at 8:26 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> > I thought, for a moment, that bash already used $'...' quoting for
> > newlines, but it turns out that's false.  At least for declare -p.
> > It would be nice if it did, though.  Newlines, carriage returns, escape
> > characters, etc.
>
> It does in some cases:
>
>   $ a=($'new \n line' $'and \e esc'); declare -p a
> declare -a a=([0]=$'new \n line' [1]=$'and \E esc')

I'd expect bash to escape any character not in the POSIX [:print:] class.

Although this is just a question of QOL improvement, since the produced 
declare statement just works as-is. It is not user friendly but code 
friendly and compact if you use the declare -p foo bar baz >savedvars.sh 
for later include savedvars.sh

--
Léa Gris

OpenPGP_signature
Description: OpenPGP digital signature