Re: terminating lines with accidental eof

[Paul Jarc]

Martin.Wheatley@jet.uk (Martin Wheatley) wrote:
> (ie commands are only executed when the user hits enter and NOT
> executed when an I/O error occurs on the input stream).

EOF is not an error.  If there is an error, then certainly bash should
not execute an partial command it has buffered, but that won't affect
your situation, since you only have EOF, not an error.

> Linking /bin/sh to /bin/bash does NOT maintain the bourne shell API.

This is well known.  I don't think Bob was recommending that you do
that.  He was just pointing out that many systems do it, and so your
statement of what /bin/sh does was ambiguous since you had not
specified which /bin/sh you're using.

> command history browsing must, similarly, present "commented"
> commands in case thay are executed as a result of this issue.

Has anyone verified that this happens for history browsing?


paul