Re: bug: --non-interactive is not global

kfogel@collab.net writes:

> Leo Savernik <l.savernik@aon.at> writes:
>> I'm not doubting the general principle at all. It's especially about the
>> --non-interactive option which is automatically perceived as an inherently
>> global option. To --non-interactive, the general principle doesn't apply, as
>> you correctly state, because it will always mean the same for any command.
>>
>> Furthermore, any command disallowing --non-interactive is non-interactive by
>> default, so there would be no contradiction in permitting --non-interactive
>> even on those commands.
>
> These are excellent points. I'm CC'ing dev@ here to see what other
> developers say. Folks, Leo's proposal is to make all non-interactive
> commands silently accept '--non-interactive', so that when writing
> scripts one can just pass it promiscuously and not worry about whether
> it's applicable or not.

Why is --non-interactive special? What about --no-auth-cache? The
arguments could even apply to --username and --password?

> Above, he points out why '--non-interactive'
> should be treated specially this way.

I'm don't really have any strong opions about the proposal, but I
don't think the script argument is a strong one. Script's are
generally "write once, use many" so I don't see why they should not be
written to pass the correct arguments.

Perhaps we should allow non-interactive to be set in the config file
instead?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org