Re: `eval` pollutes the history when it runs "set -o history"

l "set -o"' report that the "history" option is off while `eval' is running? Currently, it says me that it is on. While we are at it, are there other special behaviors of `eval` that one should be aware of, particularly regarding doing `eval $(set +o)' ? The

`eval` pollutes the history when it runs "set -o history"

Configuration Information: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash.bashrc' -DSYS_B