[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange behaviour of read builtin
From: |
Greg Wooledge |
Subject: |
Re: Strange behaviour of read builtin |
Date: |
Thu, 2 Jul 2020 07:14:43 -0400 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Thu, Jul 02, 2020 at 03:08:19AM +0300, M. Nejat AYDIN wrote:
> On 7/1/20 2:25 PM, Greg Wooledge wrote:
> > How else would you interpret "the line read is assigned to the variable
> > REPLY"? Read the line, assign it to the variable. Do not pass Go,
> > do not perform IFS whitespace trimming.
>
> Fair enough. The paragraph in which that sentence occurs contains also such
> sentences that read: "One line is read from the standard
> input,[...] split into words as described above in Word Splitting[...]"
> and "The characters in the value of the IFS variable are used to split
> the line into words [...] described above in Word Splitting".
Hmm, not in the man page. In the man page, they're in two widely
separated paragraphs. All of the options (-a aname, -d delim, ...)
lie in between them.
I have no objection to clarifying the wording, mind you. I simply
pointed out where it's documented, since you explicitly asked that.
- Strange behaviour of read builtin, M. Nejat AYDIN, 2020/07/01
- Re: Strange behaviour of read builtin, Greg Wooledge, 2020/07/01
- Re: Strange behaviour of read builtin, Eli Schwartz, 2020/07/01
- Re: Strange behaviour of read builtin, M. Nejat AYDIN, 2020/07/01
- Re: Strange behaviour of read builtin, M. Nejat AYDIN, 2020/07/02
- Re: Strange behaviour of read builtin, Chet Ramey, 2020/07/02
- Re: Strange behaviour of read builtin, M. Nejat AYDIN, 2020/07/02
- Re: Strange behaviour of read builtin, M. Nejat AYDIN, 2020/07/02