On 6/3/11 2:39 PM, Eric Blake wrote:
> Bash has a bug: ${+} is syntactically invalid, as evidenced by the error
> message when running the script, yet using 'set -n' was not able to flag
> it as an error.
It's an invalid word expansion, not a syntax error. To the parser, `${+}'
is a correctly-for
On 5/31/11 10:49 PM, Jonathan Nieder wrote:
> Explain that COLUMNS and LINES are not set automatically in
> non-interactive shells, and recommend direct use of the tput utility
> from ncurses as a replacement.
Thanks for the report, though the tput recommendation doesn't belong in
a manual page.
