On Fri, 22 Jul 2005, Greg Hudson wrote:
> On Fri, 2005-07-22 at 16:40 +0200, Peter N. Lundblad wrote:
> > I think that's confusing. I think it's better to add those options to the
> > config file.
>
> It's confusing to add them to the help output, but having them silently
> ignored by commands which don't need them wouldn't be terribly
> confusing. I don't know what we'd have to change about command-line
> parsing to introduce options which are accepted but not documented for
> certain subcommands. Perhaps we could just a list of globally-accepted
> options, and suppress the "subcommand foo doesn't accept option bar"
> error for options on that list.
>
Say we start accepting --editor-cmd as a "global" option. Then someone
runs
svn lock foo --editor-cmd=emacs
and wonders why the editor wasn't invoked to get the lock message. We
might find other such cases.
> Adding options to the config file is not equivalent. If I want to use
> "svn --username=foo" in a script, I can't add a username option to the
> config file from within the script instead, because it would interfere
> with svn executions by the user outside of the script.
>
The script could create its own config file and use --config-dir. Or it
could have a $USER_OPT variable.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 23 22:19:31 2005