bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: declare -p name=value thinks 'name=value' is variable


From: Eli Schwartz
Subject: Re: declare -p name=value thinks 'name=value' is variable
Date: Fri, 8 Jan 2021 07:24:54 -0500

On 1/8/21 4:05 AM, William Park wrote:
Another issue I came across.

     declare -p name=value

thinks 'name=value' is the variable.  My reading of manpage seems to say
'name' should be used, but not sure.  Is this a bug?

Workaround is, of course, use separate lines,
     declare name=value
     declare -p name

There's an obvious inference here, that declare -p only prints, does not create/modify, and only accepts NAMEs, therefore the optional [=VALUE] available to other modes will not be interpreted the way you seem to think it will be, in *this* mode.

--
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]