severity 297137 normal
tag 297137 sid sarge moreinfo
tag 297137 must conflict with bash << 2.05-0beta1
thanks
On Mar 17, Braun Gabor <email address hidden> wrote:
> (2) uses "unset" to unset variables which are not known to be set.
> The unset command returns non-zero when applied to a
> read-only or unset variable (see the bash man page).
Not my version of bash (nor dash, nor posh), and the man page agrees:
The exit status is true unless a name is readonly.
Looks like this was changed in bash 2.05b-beta1. Can you confirm that
your version is older?
severity 297137 normal
tag 297137 sid sarge moreinfo
tag 297137 must conflict with bash << 2.05-0beta1
thanks
On Mar 17, Braun Gabor <email address hidden> wrote:
> (2) uses "unset" to unset variables which are not known to be set.
> The unset command returns non-zero when applied to a
> read-only or unset variable (see the bash man page).
Not my version of bash (nor dash, nor posh), and the man page agrees:
The exit status is true unless a name is readonly.
Looks like this was changed in bash 2.05b-beta1. Can you confirm that
your version is older?
--
ciao,
Marco