Re: forwarded bug report

[Tanaka Akira <akr@xxxxxxxxxxx>]

In article <9906040940.AA31818@xxxxxxxxxxxxxxxxx>,
  Peter Stephenson <pws@xxxxxxxxxxxxxxxxx> writes:

> I suppose closing it is better than redirecting it from /dev/null, since
> then you get an error message which will warn the user that something
> happened which shouldn't have --- although a bit cryptic: cat gives me
>   cat: cannot stat 
> Are there cases where this is bad?

I think also that closing stdin is right behavior to show that reading
from stdin is an error in completion. But it is bit more riskey than
redirecting stdin from /dev/null.

At least, on SunOS 4.1.4, following command produces strange result.
(some-file is opend as file descriptor 0 and comm confuses.)

  comm some-file - <&-

However, intentional read from stdin like above may not appear in
copmletion.
-- 
Tanaka Akira