On Tue, Mar 25, 2014 at 2:39 AM, Pollock, Wayne wrote:
> $ echo $BASH_VERSION
> 4.2.45(1)-release
>
> $ unset foo
>
> $ foo=bar :
>
> $ echo $foo
>
>
> $
>
> ===
>
> According to POSIX/SUS issue 7, assignments for special builtins
> should persist. So the output should be ``bar''.
>
$ echo $BASH_VERSION
4.2.45(1)-release
$ unset foo
$ foo=bar :
$ echo $foo
$
===
According to POSIX/SUS issue 7, assignments for special builtins
should persist. So the output should be ``bar''.
Is there a setting I should turn off (or need to enable), to
make this work correct
Alexandre De Champeaux writes:
> Seems that the top command has nothing to do with bash. Sorry about that,
> and thanks for your fast answers. The bug is however not critical enough
> for me to spend more time searching for the real authors.
$ rpm -qif /usr/bin/top | grep URL
URL : http:
Seems that the top command has nothing to do with bash. Sorry about that,
and thanks for your fast answers. The bug is however not critical enough
for me to spend more time searching for the real authors.
Cheers,
--
Alexandre
Alexandre De Champeaux writes:
> The top command
is not part of bash, and thus off-topic.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Mon, Mar 24, 2014 at 12:08 PM, Alexandre De Champeaux
wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_
