Re: Error in read implementation and/or documentation

2013-07-27 Thread Chet Ramey
On 7/27/13 1:32 PM, Andreas Schwab wrote: > Chris Down writes: > >> Cannot reproduce. >> >> $ printf 01 | read -n3 >> $ echo $? >> 1 > > Try the same with input from the terminal. You are reading one character at a time, so ICANON is not set and ^D is an ordinary character. It's on

Re: Error in read implementation and/or documentation

2013-07-27 Thread Peter Olson
OK, that makes sense. Sorry for being confused. I thought that by this level, ^D and EOF are equivalent. I should be able to check to see if the character returned is ^D, then act accordingly. Peter On 07/27/2013 03:10 PM, Chet Ramey wrote: On 7/27/13 1:32 PM, Andreas Schwab wrote: Chris Dow

Re: Error in read implementation and/or documentation

2013-07-27 Thread Andreas Schwab
Chris Down writes: > Cannot reproduce. > > $ printf 01 | read -n3 > $ echo $? > 1 Try the same with input from the terminal. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely

Re: Error in read implementation and/or documentation

2013-07-27 Thread Chris Down
On 27 July 2013 17:17, Pierre Gaston wrote: > What is your test case? > I don't seem to be able to reproduce your problems, read returns > when it encouters EOF, and I get 1 if fewer bytes are read It seems it is something like this: $ read -n3 12^D$ echo $? 0

Re: Error in read implementation and/or documentation

2013-07-27 Thread Pierre Gaston
On Sat, Jul 27, 2013 at 8:11 PM, Peter Olson wrote: > I was using ^D as an EOF. I guess I should have tried it in other ways. Is > ^D not the same as EOF? Sorry if that is a noob question. I was able to > reproduce all of your outputs. I am using xterm as my terminal emulator, if > that matters. >

Re: Error in read implementation and/or documentation

2013-07-27 Thread Pierre Gaston
On Sat, Jul 27, 2013 at 7:37 AM, Peter Olson wrote: > According to "help read": > Options: > -n nchars return after reading NCHARS characters rather than > waiting > for a newline, but honor a delimiter if fewer than NCHARS > characters are read befo

Re: Error in read implementation and/or documentation

2013-07-27 Thread Chris Down
On 27 July 2013 19:32, Andreas Schwab wrote: > Chris Down writes: >> Cannot reproduce. >> >> $ printf 01 | read -n3 >> $ echo $? >> 1 > > Try the same with input from the terminal. Hm, that's a whole other problem then. I can reproduce this by following that path.

Re: Error in read implementation and/or documentation

2013-07-27 Thread Peter Olson
I was using ^D as an EOF. I guess I should have tried it in other ways. Is ^D not the same as EOF? Sorry if that is a noob question. I was able to reproduce all of your outputs. I am using xterm as my terminal emulator, if that matters. Peter On 07/27/2013 10:35 AM, Chris Down wrote: Hello,

Re: Error in read implementation and/or documentation

2013-07-27 Thread Chris Down
Hello, On 27 July 2013 06:37, Peter Olson wrote: > If read is invoked with the -n or -N options, then given an EOF, it returns > with a zero exit status. Cannot reproduce. $ echo $BASH_VERSION 4.2.45(2)-release $ read -n1 In addition, if it is invoked with -n 3, for example, then g

Error in read implementation and/or documentation

2013-07-27 Thread Peter Olson
According to "help read": Options: -n nchars return after reading NCHARS characters rather than waiting for a newline, but honor a delimiter if fewer than NCHARS characters are read before the delimiter Exit Status: The return code is