# from Austin Schutz
# on Friday 09 March 2007 03:11 pm:
>There are cases where terminal programs use STDIN and STDOUT
>in addition to /dev/tty, such as ssh. One can redirect the input
>and output from the remote host, yet ssh will interact with the user
>via the tty for passwords, etc. where necessary. This seems like
> natural behavior. It removes out of band interaction from getting
> tossed in with the in band data.
Hmm, maybe prompting on the tty when not -p STDOUT is an option that
might be worth exploring. But, EU::MM has set a precedent for how
automation interacts with it, so I don't think requiring automation to
be done via `expect` and such is the solution.
I think it's worth noting that `rm` prompts on STDERR. I'll leave it up
to the reader to ponder that.
> Maybe that's what you're suggesting already. I've gotten a
> little lost in this thread in terms of figuring out who is arguing
> for what and under what circumstances.
It basically comes down to deciding whether or not Build.PL should be
rude to the user (in typical unix fashion) or require (IMO strange)
half-interactive batch jobs to do something special like (gasp!) set an
environment variable.
--Eric
--
"Everything should be made as simple as possible, but no simpler."
--Albert Einstein
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
