Re: [RFC] [PATCH] Use console, not stdin/stderr, for prompting

[Peter Samuelson]
> I'd say, if you don't have an actual console at hand, you really
> really should be using --non-interactive.

Alternatively, I considered doing this same thing, but falling back to
stdin / stderr if the console cannot be opened. apr_password_get()
seems to use them if there is no native getpass() facility.

I'm still leaning toward just failing outright when trying to prompt
when there is no console, like we do in --non-interactive mode, but I
could be persuaded otherwise, if you think there are likely to be apps
that need to 'screen scrape' a command line tool (instead of using our
API) and that we should support this.

I _am_ rather curious whether, on Windows, using "CON:" for prompting
actually allows stdin to be usable for other things. Like, when piping
or redirecting to it. I suppose I can try to test this feature using
MingW32 + Wine, but that seems to be the sort of corner case where
MingW32 + Wine might or might not behave the same as real Windows.

-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/