> -----Original Message-----
> From: hy...@hyrumwright.org [mailto:hy...@hyrumwright.org] On Behalf Of
> Hyrum K. Wright
> Sent: maandag 20 december 2010 23:29
> To: Subversion Development
> Subject: Default commandline args
>
> In issue #3765, I suggest the possibility of a CVS-style config file
> wherein a user could specify a set of default arguments for a given
> subcommand. For example, 'svn diff' would default to 'svn diff -x -p'
> if the config file had an entry for such. Thinking this would be an
> SMOP, I jumped in...only to discover that it isn't.
>
> The actual implementation isn't hard, I'm just wondering about where
> the configuration should live. We have a ~/.subversion/config file,
> but these options aren't for the client library, they are specific to
> the commandline client. This makes me think that we should have a
> separate file for the commandline client, and that it may want to be
> something like ~/.svnrc or something equally commandline-ish.
I remember reading (from some far earlier discussions) that we had specific
reasons not to implement these options here. (Deliberate decision against
the CVS design)
One reason I could think of (without looking at those discussions) is that
it would break shell scripts that just use 'svn <some options>'.
(Especially if someone would add a -u to status, like one of the examples)
Another reason might be that 'svn <options>' works differently on one system
then on another one when the config file changes, but I don't think this a
strong argument as we already change output in some cases. (E.g. diff
options)
But as long as the options are in the svn client, easy to override and not
(by default) used from plain libsvn_client, I don't have a strong opinion
for or against this.
Bert
