GNU bug report logs - #22803
bash printf and negative precision

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22803 in the body.
You can then email your comments to 22803 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Billerbeck, Dirk" <dirk.billerbeck <at> dataport.de>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: bash printf and negative precision
Date: Thu, 25 Feb 2016 07:18:24 +0000

[Message part 1 (text/plain, inline)]

Hello,

I don't know if it's really a bug, if I'm just mistaken or this is the right address but I just want to give it a try.

I'm using the following bash-builtin printf command:

FUELLLAENGE=8 ; report="REPIBZVAG" ; REPORTFUELLZEICHEN="0" ; printf '%.8s%*.*d\n' $report 0 $((FUELLLAENGE - ${#report} )) "$REPORTFUELLZEICHEN"

The maximum length of $report  is 8 characters but I tested some possible error situations so in this example it is 9 characters log. I would expect printf to cut the $report from REPIBVZAG to REPIBZVA and to NOT print any additional trailing zeros because of the precision value of -1. But a trailing zero is printed (set -x output):

+ FUELLLAENGE=8
+ report=REPIBZVAG
+ REPORTFUELLZEICHEN=0
+ printf '%.8s%*.*d\n' REPIBZVAG 0 -1 0
REPIBZVA0

Is this really correct? Or shouldn't the negative precision be taken as zero and no character should be printed?

The bash version is "GNU bash, version 3.2.51(1)-release (x86_64-suse-linux-gnu)". I know it's an older version but I can't change it as there are corporate restrictions. The coreutil package is "coreutils-8.12-6.25.32.33.1".

Best regards
Dirk Billerbeck

[Message part 2 (text/html, inline)]

Message #8 received at 22803 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: "Billerbeck, Dirk" <dirk.billerbeck <at> dataport.de>
Cc: 22803 <at> debbugs.gnu.org
Subject: Re: bug#22803: bash printf and negative precision
Date: Thu, 25 Oct 2018 09:55:37 -0600

tags 22803 notabug
close 22803
stop

(triaging old bugs)

On Thu, Feb 25, 2016 at 07:18:24AM +0000, Billerbeck, Dirk wrote:
> Hello,
> 
> I don't know if it's really a bug, if I'm just mistaken or this is the right address but I just want to give it a try.
> 
> I'm using the following bash-builtin printf command:
> 
> [...] 
> 
> The bash version is "GNU bash, version 3.2.51(1)-release (x86_64-suse-linux-gnu)". I know it's an older version but I can't change it as there are corporate restrictions. The coreutil package is "coreutils-8.12-6.25.32.33.1".
> 

It seems your message was lost and not replied to in 2 years. Sorry about that.

Your question is about bash's "printf", so it should be sent to help-bash <at> gnu.org
(or bug-bash <at> gnu.org if you suspect a bug).

This mailing list is for GNU coreutils (which also provides a 'printf' program,
but not bash's built-in one).

As such, I'm closing this bug.

-assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.