Re: printf %m$ and %*m$ unimplemented in Bash, but implementated in C compilers

>I guess it could be more explicit Yes, that is essentially what I was asking for. There are several standards for printf, and it was ambiguous which one was being referred to. There's the C standards, the POSIX standards, and the Single Unix Specifications. I didn't know which one was being refer

Re: printf %m$ and %*m$ unimplemented in Bash, but implementated in C compilers

"The 'printf' in shells is different than the 'printf' specified by ISO C/POSIX. The documentation for the bash built-in can be found here: $ info '(bash)Bash Builtins' The 'printf' provided in your C library should be found in man page section 3. Your system probably comes with a program (no

Re: compute_lcd_of_matches w/ mismatched upper/lowercase byte counts

On 5/24/24 4:02 AM, Grisha Levit wrote: This requires case-insensitive completion of two+ words where the the prefix in a word contains the single-byte lowercase form of the multi- byte character occuring in the same position in an earlier word. Thanks for the report. Common prefixes of differe

[PATCH] read: free ifs_chars

Avoid leaking ifs_chars on more return paths. --- builtins/read.def | 16 1 file changed, 16 insertions(+) diff --git a/builtins/read.def b/builtins/read.def index 37328efc..69a1ef4c 100644 --- a/builtins/read.def +++ b/builtins/read.def @@ -635,6 +635,8 @@ read_builtin (WORD_LIS