Re: [sr #111166] ngettext syntax

May be some orthogonality regarding %d expecting a string vs num-expr $ a=1234 i=1 $ echo ${a:i+1} 34 $ echo ${a:$((i+1))} 34 $ Why do we have this 'offset' evaluated, you could use the same argument you used for printf that is $((...)) is good enough, add clarity, remove ambiguity and the docco

Re: How to fix this

what u wanna fix on it On Mon, Feb 24, 2025, 3:13 PM rjuliuscezar--- via Bug reports for the GNU Bourne Again SHell wrote: > usage: command-not-found > > ╭─u0_a440@localhost ~ > ╰─🍄💨➤➤ > >

Re: [sr #111166] ngettext syntax

On Mon, Feb 24, 2025 at 8:22 AM Martin D Kealey wrote: > > > On Mon, 24 Feb 2025 at 13:48, Phi Debian wrote: > >> I also forgot to mention that C99 introduced this >> >>There may be no gaps >>in the numbers of arguments specified using '$'; for example, if >> argu‐ >>men

How to fix this

usage: command-not-found ╭─u0_a440@localhost ~ ╰─🍄💨➤➤

Re: [sr #111166] ngettext syntax

On 2/22/25 4:38 AM, Phi Debian wrote: This way pure unumbered (no mixed indexed) works as before (as we used to) Pure numbered (no unumbered) works as it does in C. Mixed depart from C (as do fmt re-use) and the rule of thumb is easy to remember, count unnumbered as they appears, and numbered a

Re: [sr #111166] ngettext syntax

On 2/22/25 5:05 AM, Phi Debian wrote: On Sat, Feb 22, 2025 at 9:49 AM Andreas Schwab > wrote: On Feb 22 2025, Phi Debian wrote: > I forgot to mention your trick to nuke the fmt reuse still works > > $ printf '%s %s %s %999$s' A B C D E F G

Re: [sr #111166] ngettext syntax

On 2/22/25 6:33 PM, Robert Elz wrote: Further, this spec also violates Chet's rule: chet.ra...@case.edu said: | There is no user who would think that using a numbered conversion specifier | is not an absolute position in the original argument list. which does not apply when the format st

Re: [sr #111166] ngettext syntax

On 2/22/25 11:17 PM, Phi Debian wrote: - if allowing mix and match numbered/unumbered then stays away from unumbered following a numbered mean the unumbered is last the numbered+1 this is tempting but wrong, i.e '%3$s %s' one would be tempted to say %s is equiv to %4$s, but the width.prec preda

Re: [sr #111166] ngettext syntax

On 2/23/25 10:48 PM, Phi Debian wrote: > Again the rule I used for ksh93 is that the next arg for fmt reuse is > max( number_of_unumbered_occurences, highest_numberd_index ) So you make numbered conversion specifiers relative to some max base from the previous scan through the

Re: [sr #111166] ngettext syntax

On Mon, Feb 24, 2025 at 4:14 PM Chet Ramey wrote: > > > > > The beast of burden is already done in bash, it does scan the fmt string > > recognise integer conversion specifier fetch the arg 'string' and apply > an > > integer validity test on it, this is on this last operation that the > > validi