mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ron Yorston <>
Subject: Re: [musl] print does not support variable width plus padding
Date: Thu, 16 Dec 2021 11:22:34 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Rich Felker <> wrote:
>FWIW I suspect the problem is that Busybox is not recognizing the 0
>character as a flag (which it is, in the printf grammar) and thinks
>it's the leading character of a width, making the * specifier for
>width invalid (since a width was already seen).

Quite so.  0 was missing from the list of valid flag characters.
Moreover only one flag character was being processed so the format
'%0 d', for example, was also considered invalid.

I've submitted a patch to BusyBox.


      parent reply	other threads:[~2021-12-16 11:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 15:22 Andrew Snyder
2021-12-14 16:03 ` Szabolcs Nagy
2021-12-14 16:09   ` Andrew Snyder
2021-12-14 16:10     ` Andrew Snyder
2021-12-14 16:50       ` Rich Felker
2021-12-14 17:05         ` Andrew Snyder
2021-12-15 18:09       ` Quentin Rameau
2021-12-15 18:37         ` Andrew Snyder
2021-12-15 21:21           ` Rich Felker
2021-12-15 21:40             ` enh
2021-12-15 21:51               ` Andrew Snyder
2021-12-16 11:22             ` Ron Yorston [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).