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 with a usage pattern like this:
>
> global_svn_opts="--non-interactive ..." # non-interactive because it is a
> script
>
> ...
>
> svn $global_svn_opts up ...
>
> ...
>
> svn $global_svn_opts switch ...
>
> ...
>
> svn $global_svn_opts revert # ERROR: will complain here, but should not
>
>
> 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.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 11 21:10:05 2005