Am Montag, 11. Juli 2005 20:14 schrieb kfogel@collab.net:
> Leo Savernik <l.savernik@aon.at> writes:
> > I've noticed that --non-interactive produces errors on certain commands
> > like "revert". This makes it unnecessarily complicated to use svn from
> > within a script
[...]
> > It would be cleaner to accept --non-interactive as a global option,
> > even if it takes no effect for the current command instead of aborting.
>
> The same question has come up for many options, and we decided it was
> better to keep each individual command's option space clean (and error
> when inapplicable options are passed) than start being loose. There
> are various reasons for this. One is that by silently accepting an
> option but doing nothing with it, a subcommand effectively closes off
> the possibility of doing anything useful with that option in the
> future. This concern probably doesn't apply to --non-interactive in
> this case, but as a general principle it still holds.
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.
>
> -Karl
mfg
Leo
PS: Please CC me, I'm not subscribed
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 11 22:48:04 2005