Paul Eggert wrote:
> my earlier patch
> neglected the possibility that mbrtowc can return 0
I wouldn't see this as a bug: You can assume that mbrtowc returns
0 if and only if the multibyte sequence is a NUL byte - but you had
chosen srcend in such a way that this would not happen in the loop.
>
Hi,
coreutils 8.29-1 on Arch Linux.
$ date -uIs -d @-62135596801
-12-31T23:59:59+00:00
$ date -uIs -d @-12-31T23:59:59+00:00
date: invalid date ‘@-12-31T23:59:59+00:00’
$
If date thinks it's valid ISO 8601 when it outputs it,
I'd ex
Dear GNU folks
I believe I have found a bug in ls in the GNU coreutils v. 8.22.
My colleague and I found that 'ls' reported a different date for a gzipped log
file when run with different options in a directory containing a large amount
of data (1000MB).
In the full listing we saw that date n
tag 32289 notabug
close 32289
thanks
On 07/27/2018 11:41 AM, Ludovic Tolhurst-Cleaver wrote:
> Dear GNU folks
>
> I believe I have found a bug in ls in the GNU coreutils v. 8.22.
>
> My colleague and I found that 'ls' reported a different date for a gzipped
> log file when run with different op
Apologies again folks: ls -ltc and ls -lt output different information
by design.
Please forgive me wasting your time.
L.
Forwarded Message
Apologies - here is the OS information:
$ cat /proc/version
Linux version 3.10.0-862.3.3.el7.x86_64
(buil...@kbuilder.dev.centos.org
Forwarded Message
Apologies again folks: ls -ltc and ls -lt output different information
by design.
Please forgive me wasting your time.
L.
Forwarded Message
Apologies - here is the OS information:
$ cat /proc/version
Linux version 3.10.0-862.3.3.el7
Apologies - here is the OS information:
$ cat /proc/version
Linux version 3.10.0-862.3.3.el7.x86_64
(buil...@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat
4.8.5-28) (GCC) ) #1 SMP Fri Jun 15 04:15:27 UTC 2018
Many thanks
LTC
Forwarded Message
Dear GNU folks
Bruno Haible wrote:
You can assume that mbrtowc returns
0 if and only if the multibyte sequence is a NUL byte - but you had
chosen srcend in such a way that this would not happen in the loop.
Thanks for the correction. I mistakenly thought that C allows multibyte
encodings in which a null wide
