-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
kfogel@collab.net wrote:
> By default, 'svn help' would only show the commonly-used commands
> that a new user would be most likely to want to see in help output.
> It would end with instructions to use 'svn help -v' to see the full
> list of commands. Something like this:
[snip]
> Running 'svn help -v' would simply give the same output that 'svn
> help' currently produces, or something very close to that.
[snip]
> Implementation is straightforward: Have a new boolean flag on each
> command in main.c's command table. Iff the flag is set, include the
> command in 'svn help' output. Just ignore the flag if -v is passed,
> just unconditionally list every command.
>
> Thoughts?
>
> -Karl
It seems like an excellent idea to me.
In terms of implementation, might it be more extensible to use something
like 'svn help all'? With 'svn help -v' you're limited to all or
nothing. At some later stage it might be desireable to add help
categories. For example just off the top of my head (i.e. hastily
thought out, forced examples) 'svn help wc' to list commands to
manipulate working copies or 'svn help forking' for branch, merge, tag,
etc.. I'm thinking of something like perldoc, if that helps any.
Even if categories are never implemented it might not hurt to have the
help system able to arbitrarily filter commands. On the other hand, I
may be violating the KISS principle.
Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC0s1LP/oUEZ9g59cRAj+qAJwI6SUwPU7uPDBrby/CwcHiLLfmbwCfRaHc
wmH6lXdqIsP5mJ6rnNaauqE=
=Smk8
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 11 22:49:01 2005