bzr svn propedit equivalent

[Kent Gibson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jari Aalto wrote:
> Kent Gibson <warthog618 at gmail.com> writes:
>> To me that sounds more like an argument for shareable aliases or
>> tab completion, not for builtin aliases.
>
> Again, those "tab completions" need to be installed separately.
> Shareable aliases too. Keep in mind that The "su" may have nothing
> to do with your account.
>
>>> This will not help scripts and error checking. It is better to
>>> require
>>>
>>> bzr config get --all
>>>
>>> And with
>>>
>>> bzr config get
>>>
>>> print reasonable error message for missing parameter.
>>>
>> I don't get the point about scripts and error checking. I've seen
>> it in other threads and I still don't get it.
>
> I suppose that you're somewhat familiar with shell scripting, so
> you know these:
>
> make && make install
>
> The second command is executed only when the first succeeds. On
> error, the statements "do not chain". Similarly for bzr commands in
> scription case:
>
> bzr ... && bzr ...
>
> If there is a call:
>
> config get variable "$options"
>
> And $options is empty, for whatever reasons, from shell's point of
> view, the commands reads:
>
> config set variable
I presume you mean "get", or more likely you meant the initial "get"
to be "set".
I agree that you would want the set case to error, cos that can lose
config.
But that is not related to the script robustness issue.
>
> If program has some defaults when *no* *arguments* are given, this
> gives surprising results. Therefore the above will and should print
> error and not assume e.g. "" empty value.
I can see where you are coming from but I don't see this as a bzr problem.
I see this as the script writer's problem.
If $options being non-existent can cause unexpected results then check
that is never is - in the script.

>
> Similarly for all other ocmmands. Like requiring "--all" to catch
> the missing intentions.
>
And that is an argument for banning optional arguments.
In that case we need to fix status, ls, pull, .....


Cheers,
Kent.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF7CP+goxTFTi1P8QRAu1nAJ4g7mF5LsDGBcxG0gLEyTOTwpokOQCg67/P
rWoNogYvFGYsJFB9X4N0VZw=
=ESAG
-----END PGP SIGNATURE-----