Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15017
| From | mike b <michallinuxstuff@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Reading from a file by using its FD returns its contents only once |
| Date | 2018-12-31 18:19 +0100 |
| Message-ID | <mailman.6627.1546276767.1284.bug-bash@gnu.org> (permalink) |
| References | <CACosJgxBTuPp9KpUuT5nST9dB7uFqP2gJ31q76C8O9owRU7_iw@mail.gmail.com> <CAN-HRFYUThxx6XwT59XHZoevdYOJRT3e6wLfS8A+yd+2w5hmvg@mail.gmail.com> |
That's a good point, I haven't thought about it like this. I always thought
that each read always starts at the beginning of the file given fd points
at. So the fact that it changes offset is a bit surprising:
# echo word >t
# exec {in}<t
# read -rn1 -u"$in"; echo "$REPLY"
w
# read -rn1 -u"$in"; echo "$REPLY"
o
# read -rn1 -u"$in"; echo "$REPLY"
r
# read -rn1 -u"$in"; echo "$REPLY"
d
I mean, it's surprising to me, I am not saying it's bad behavior or
anything.
Anyways, thanks for your feedback Tadeus. :)
pon., 31 gru 2018 o 17:40 Tadeus Prastowo <tadeus.prastowo@unitn.it>
napisaĆ(a):
> On Mon, Dec 31, 2018 at 2:37 AM mike b <michallinuxstuff@gmail.com> wrote:
>
> [...]
>
> > The above is just an example. Doing reads on any other regular file like
> > this yields same behavior:
> > # echo bla >./t
> > # exec 10<./t
> > # read -r <&10
> > # echo $REPLY
> > bla
> > # read -r <&10
> > # echo $REPLY
>
> That's correct behavior because the second `read -r' already hits an
> EOF, isn't that?
>
> --
> Best regards,
> Tadeus
>
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Reading from a file by using its FD returns its contents only once mike b <michallinuxstuff@gmail.com> - 2018-12-31 18:19 +0100
csiph-web