Date: Wed, 8 Feb 2023 10:24:33 +0000 (UTC)
From: "Thorsten Glaser via austin-group-l at The Open Group"
<austin-group-l@opengroup.org>
Message-ID: <pine.bsm.4.64l.2302081021300.7...@herc.mirbsd.org>
| However, executing the partial line after getting a read error
| can and probably should be treated differently *unless* a read
| error is treated as EOF.
I agree with that - the error is either an error, which would cause
a non-interactive shell to immediately exit with non-zero exit status
(with some message on stderr), or an interactive shell to return to the
command prompt, issue a new PS1, start a new read, presumably get an
error again, ....
If the read error is treated as EOF, then the shell acts just like any
other EOF at that point.
I have no problem with specifying the "must be EOF" behaviour (yash could
change) but requiring it to be treated as an error, rather than just allowing
it, would be a non-starter given that only yash (that we know of) behaves
that way. I however don't object to it being unspecified which behaviour
will occur - of those two. This is not a case where it needs to simply be
unspecified what happens, such that the shell can do anything it likes.
kre
