bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Simon Wolfe
How does ls version 9.4 do with code points not yet used ? I'm asking because it seems it takes 2 years for changes to make it to distros; it might be a good idea to code things ahead... Like if you use U+40500 ( 񀔀 ) and type touch ''$'\361\200\224\200' ls ''$'\361\200\224\200' will it show

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Paul Eggert
On 2024-09-12 12:03, Pádraig Brady wrote: This is tricky enough, that we should be as restrictive as possible here, so I may resort to strspn(f, "0123456789") to parse instead. I'll think a bit about it. The code's also assuming INT_MAX < INTMAX_MAX, which POSIX doesn't require. You could pu

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 12/09/2024 18:40, Collin Funk wrote: Hi Pádraig, Pádraig Brady writes: I'll apply the attached sometime tomorrow. Marking this as done. Patch looks good, thanks. One small comment, though. +#define GET_CURR_ARG(POS) \ +do {

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 12/09/2024 18:06, Bruno Haible wrote: Pádraig Brady wrote: I'll apply the attached sometime tomorrow. Nice! Thank you. There seems to be a typo in the unit test, though: It defines a shell function 'printf_checki_err' but the function it then invokes is 'printf_check_err'. Hah, good catc

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Collin Funk
Hi Pádraig, Pádraig Brady writes: > I'll apply the attached sometime tomorrow. > > Marking this as done. Patch looks good, thanks. One small comment, though. > +#define GET_CURR_ARG(POS)\ > +do { \ > + char *arge;

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Bruno Haible
Pádraig Brady wrote: > I'll apply the attached sometime tomorrow. Nice! Thank you. There seems to be a typo in the unit test, though: It defines a shell function 'printf_checki_err' but the function it then invokes is 'printf_check_err'. Bruno

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 09/09/2024 19:30, Pádraig Brady wrote: On 06/09/2024 15:06, Bruno Haible wrote: Hi, POSIX:2024 specifies that printf(1) should support numbered conversion specifications: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/printf.html https://austingroupbugs.net/view.php?id=1592 Coul

bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Simon Wolfe
On 2024/09/12 19:42, Pádraig Brady wrote: On 12/09/2024 11:16, Simon Wolfe wrote: I have one file name that uses Unicode character U+318DF, which is in the tertiary pane, more precisely CJK Unified Ideographs Extension H. touch 𱣟 ls returns: ''$'\360\261\243\237' Extension H was introduced

bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Pádraig Brady
On 12/09/2024 11:16, Simon Wolfe wrote: I have one file name that uses Unicode character U+318DF, which is in the tertiary pane, more precisely CJK Unified Ideographs Extension H. touch 𱣟 ls returns: ''$'\360\261\243\237' Extension H was introduced in Unicode 15.0 in 2022. I also notice tha

bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Thomas Wolff
Am 12.09.2024 um 12:16 schrieb Simon Wolfe: I have one file name that uses Unicode character U+318DF, which is in the tertiary pane, more precisely CJK Unified Ideographs Extension H. touch 𱣟 ls returns: ''$'\360\261\243\237' I use a wrapper with my favourite options and a pipe to stop ls f

bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Simon Wolfe
I have one file name that uses Unicode character U+318DF, which is in the tertiary pane, more precisely CJK Unified Ideographs Extension H. touch 𱣟 ls returns: ''$'\360\261\243\237' Extension H was introduced in Unicode 15.0 in 2022. I also notice that this bug occurs with any character with