Re: 0xFF and read -N

[Chet Ramey]

On 8/31/13 3:13 PM, Stephane Chazelas wrote:

> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
> 
> When called with the -N option, "read" seems to consider the byte 0xFF
> as meaning EOF (well, not exactly since it doesn't set the exit status to
> non-zero)

Not quite: it interprets that as satisfying the delimiter, since the delim
is set to -1.  It needs to test an additional flag.  I've made that fix,
and the fix will be in bash-4.3.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/