[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Default commandline args

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 21 Dec 2010 13:15:17 +0200

Bert Huijben wrote on Tue, Dec 21, 2010 at 10:00:37 +0100:
> > -----Original Message-----
> > From: hyrum_at_hyrumwright.org [mailto:hyrum_at_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.

How about having ~/.subversion/clients/${client_name}/

and then svn/main.c just calls svn_config_bikeshed(client_name='cmdline').

> 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)

Agreed that we should have an option to override the default --- e.g.,
to force 'status' to run without -u.

> 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
Received on 2010-12-21 12:18:14 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.