Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Bob Proulx
Cuong Manh Le wrote: > I'm sorry for that. It's not the time between post but after sending the > email, I look at the help-bash archive and see it have no active email > since January. There has been lots and lots of email in the archive since January. http://lists.gnu.org/archive/html/help-ba

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Cuong Manh Le
Hi Bob, I'm sorry for that. It's not the time between post but after sending the email, I look at the help-bash archive and see it have no active email since January. Anyway, still my fault. Thanks. On Wed, Feb 24, 2016 at 11:58 PM, Bob Proulx wrote: > Greg Wooledge wrote: > > On Wed, Feb 24,

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Bob Proulx
Greg Wooledge wrote: > On Wed, Feb 24, 2016 at 11:31:40AM +0700, Cuong Manh Le wrote: > > I send this email to help-bash but it seems to be inactive. Please help me > > with this problem. Thanks. > > help-bash is active. You probably just didn't wait long enough. > If this is your first message t

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Greg Wooledge
On Wed, Feb 24, 2016 at 09:45:02PM +0700, Cuong Manh Le wrote: > If you put it into a while loop context: > > while read -d '' line; do echo "$line"; done < <(printf '1') > > > give you nothing. There's only one read in this case > > There's data to read, but read return non-zero there. it does

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Cuong Manh Le
Why there's no different? EOF means you have nothing to read. If you put it into a while loop context: while read -d '' line; do echo "$line"; done < <(printf '1') give you nothing. There's only one read in this case There's data to read, but read return non-zero there. it doesn't find delimit

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Greg Wooledge
> > It's the same thing. "Reached EOF before seeing the delimiter" is the > > whole, combined reason. > > How can we verify it? > > Stephane Chazelas also have the same opinion with me in his answer > http://unix.stackexchange.com/a/265484/38906, that's error came from no > delimiter found. You

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Cuong Manh Le
> > It's the same thing. "Reached EOF before seeing the delimiter" is the > whole, combined reason. How can we verify it? Stephane Chazelas also have the same opinion with me in his answer http://unix.stackexchange.com/a/265484/38906, that's error came from no delimiter found. IMHO, it will be

Re: Fwd: read builtin return non-zero status reason

2016-02-24 Thread Greg Wooledge
On Wed, Feb 24, 2016 at 11:31:40AM +0700, Cuong Manh Le wrote: > I send this email to help-bash but it seems to be inactive. Please help me > with this problem. Thanks. help-bash is active. You probably just didn't wait long enough. If this is your first message to help-bash, your message is prob