Dear DEV TEAM,
I want to report a strange *printf* behaviour which appears in debug mode +
no arguments.
OS: Debian GNU/Linux 12 (bookworm)
BASH_VERSION="5.2.15(1)-release"
OS: MACOS
BASH_VERSION="5.2.21(1)-release"
The culprit function is *printargs() { printf "%s|" "$@"; echo; }*
calling it
On Thu, Feb 08, 2024 at 05:48:18PM +0200, Timotei Campian wrote:
> The culprit function is *printargs() { printf "%s|" "$@"; echo; }*
>
> calling it with no arguments it prints as expected the pipe: "|"
> while in debug mode (set -x), only a *blank line* is printed:
>
> $ printargs
> printargs
>
On Wed, Feb 7, 2024 at 2:24 AM Grisha Levit wrote:
> Maybe it would be appropriate to reject a request to turn off an
> attribute that is being turned on?
>
Since this seems specific to indexed and associative arrays, it might make
more sense to just give the same error you get if you try to uns
On 1/31/24 2:35 PM, Robert Elz wrote:
| Not quite. `new' in this sense is the opposite of `anything in the past'
| as Dale described it -- already notified and removed from the jobs list.
I guess the part about bash that I am not understanding here is how the
"already notified" works. T
