bzr svn propedit equivalent
Sabin Iacob
iacobs at m0n5t3r.info
Sun Mar 4 09:51:17 GMT 2007
Jari Aalto wrote:
> Error is better, because then it would correctly stop script with
> empty "$variable". Add option --edit:
>
> $ bzr config set --edit variable
>
sounds good; an editor is useful when you may want multi-line variables,
but you would probably rarely use that
> And make this display error when no consequent argument in line is
> found after "variable":
>
> $ bzr config set variable
> ERROR: set operatiof of `variable' is missing value par
>
that's as easy as throwing BzrCommandError
>> Other bits I'd like to see include a get --all and/or having that as
>> the default if no option is specified.
>>
this is a bit more complicated, due to having several config stores
>> I'd also like a sub command to remove an option from a config file,
>> say remove or reset.
>> e.g. bzr config --location reset email
>>
again, complicated; I'll have to subclass BranchConfig for the 2 above
features, because there is no "dump" and "remove" functionality
> It's better to stay in same commands sa bzr itself; "remove" and alias
> "rm":
>
> $ bzr config rm [option] {variable}
>
> Possible options:
>
> --all remove all
> --regex=RE Remove variables by regexp RE
>
> Jari
>
unless there is some class I don't know about (quite possible,
actually), there is no support for subcommands with specific options and
aliases, so this would need to be implemented by hand; and it'll grow
big, and I'm horrified about writing tests, because I've never done that
(never needed), so I wouldn't know where to start and where to finish :)
More information about the bazaar
mailing list