Re: RFE: enable buffering on null-terminated data

On Sun, Mar 10, 2024 at 4:36 PM Carl Edquist wrote: > > Hi Zack, > > This sounds like a potentially useful feature (it'd probably belong with a > corresponding new buffer mode in setbuf(3)) ... > > > Filenames should be passed between utilities in a null-terminated > > fashion, because the null

Re: RFE: enable buffering on null-terminated data

Hi Zack, This sounds like a potentially useful feature (it'd probably belong with a corresponding new buffer mode in setbuf(3)) ... Filenames should be passed between utilities in a null-terminated fashion, because the null byte is the only byte that can't appear within one. Out of

'wc -m' and combining characters

I'm attempting to learn about UTF-8. My question is about how wc counts "combining characters", as discussed here . I made two files, one with "LATIN CAPITAL LETTER A WITH DIAERESIS" called p1.txt. The other with "LATIN CAPITAL LETTER A"

RFE: enable buffering on null-terminated data

Was "stdbuf feature request - line buffering but for null-terminated data" See below. On Sun, Mar 10, 2024 at 5:38 AM Pádraig Brady wrote: > > On 09/03/2024 16:30, Zachary Santer wrote: > > 'stdbuf --output=L' will line-buffer the command's output stream. > > Pretty useful, but that's looking

Re: stdbuf feature request - line buffering but for null-terminated data

On 09/03/2024 16:30, Zachary Santer wrote: 'stdbuf --output=L' will line-buffer the command's output stream. Pretty useful, but that's looking for newlines. Filenames should be passed between utilities in a null-terminated fashion, because the null byte is the only byte that can't appear within