On 2/6/14, 10:39 AM, Branko Čibej wrote: > Not in general; the pager intercepts stdout, but we prompt to and read > responses directly from the terminal. Only in extreme cases do we fall back to > prompting to stderr and reading responses from stdin. All of the above is true > for Windows, too. > > When I rewrote the terminal abstraction for prompting, I tested it by > redirecting both stdout and stderr to /dev/null; and I still got the prompts > in > the terminal.
I stand corrected, you're right it does work properly in spite of the pager. I just tried svn blame with the automatic pager functionality enabled and using less against a server that required authentication (and with --config-dir /var/empty to force prompting). It worked perfectly. I still think --non-interactive is not a replacement for --no-pager since in the same example if I use --non-interactive my command doesn't run (errors out on authenticatoin).
