Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
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: Mon, 31 Dec 2018 18:19:06 +0100
Lines: 46
Approved: bug-bash@gnu.org
Message-ID: <mailman.6627.1546276767.1284.bug-bash@gnu.org>
References: <CACosJgxBTuPp9KpUuT5nST9dB7uFqP2gJ31q76C8O9owRU7_iw@mail.gmail.com> <CAN-HRFYUThxx6XwT59XHZoevdYOJRT3e6wLfS8A+yd+2w5hmvg@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: Tadeus Prastowo <tadeus.prastowo@unitn.it>, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAN-HRFYUThxx6XwT59XHZoevdYOJRT3e6wLfS8A+yd+2w5hmvg@mail.gmail.com>
Precedence: list
Xref: csiph.com gnu.bash.bug:15017

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=C5=82(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 lik=
e
> > 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
>