Fabien COELHO wrote:
> Yet another submission. I like to complete what I start...
> It addresses Julian comments on v4.
OK, thanks. I have committed this version 5 (with cosmetic tweaks to comments
and white space) in r17458.
> Julian, if you don't like the two beeps/spaces, just remove the
> offending line so that it defaults to ordinary file completion. I may
I don't like it, but as you prefer it that way and you are more interested in
using this than I am, I have left it that way.
> look later to your suggestion about removing the default completion from
> "complete" and then add it back later when appropriate with "compgen".
> Improve bash auto-completion for the 'svn' command:
> - there is a "real" parser to check for what is available
> and deduce what can be suggested further.
> - although it is not a good practice, mixed options and arguments
> is supported by the completion as it is by the svn command.
> - the completion works in the middle of a line.
> - property names are completed: see comments about issues related to
> ":" within property names although it is a word completion separator...
> - user-defined file and revision properties can be added with
> environment variables SVN_BASH_FILE_PROPS and SVN_BASH_REV_PROPS.
> - unknown properties are assumed to be simple file properties.
> - --revprop and --revision options are forced to revision properties
> as they are mandatory in this case.
> - argument values are suggested to some other options, eg directory names
> for --config-dir.
> - values suggested to some options can be extended with environment
> so as to keep the default completion list short.
> * tools/client-side/bash_completion
> add shell-intelligence to _svn completion function
I moved the comments about what it does into the file, and left in the log
message only a brief summary of what was changed.
I hope this is OK. Thanks for your patience.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Nov 20 22:47:37 2005