bug#14299: Incorrect output of `printf "\\n"`

2013-04-29 Thread Pavel Elkind
Dear developers, I found the following potential bug in printf (version 8.17). Actual result: `printf "\\n"` prints a newline caracter. Expected result: `printf "\\n"` prints a sequence of two individual characters, '\' and 'n', like '\n', but not a newline character. Please address the abo

bug#13127: [PATCH] cut: use only one data strucutre

2013-04-29 Thread Philipp Thomas
Am 28.04.2013 04:40, schrieb Pádraig Brady: > 2. When --output-delimiter is specified, it will allocate 31 buckets. > Even if a few ranges are specified. Shouldn't this be "Even if only a few ranges are specified"? Philipp

bug#14299: Incorrect output of `printf "\\n"`

2013-04-29 Thread Eric Blake
tag 14299 notabug thanks On 04/28/2013 12:44 PM, Pavel Elkind wrote: > Dear developers, > > I found the following potential bug in printf (version 8.17). > > Actual result: > `printf "\\n"` prints a newline caracter. Of course. That's what POSIX requires it to print. $ set -x $ printf ".\\n.

bug#14299: Incorrect output of `printf "\\n"`

2013-04-29 Thread Davide Brini
On Sun, 28 Apr 2013 18:44:23 +, Pavel Elkind wrote: > Dear developers, > > I found the following potential bug in printf (version 8.17). > > Actual result: > `printf "\\n"` prints a newline caracter. > > Expected result: > `printf "\\n"` prints a sequence of two individual characters, '\'

bug#14318: sort: unexpected results

2013-04-29 Thread Kenneth Dickman
Why does putting "depot" in the input file, corrupt the sort function? How can I get sort to operate properly? $ cat good bin/... //b/bin/... logs/... //logs/... ... //b/... $ sort good ... //b/... bin/... //b/bin/... logs/... //logs/... $ cat bad bin/... //depot/b/bin/... logs/... //depot/logs/.