Proper command line arguments

[John A Meinel]

I've been having difficulty figuring out what the order of command line
arguments should be. Once we start having more and more commands that
take a remote branch as well as a local one, what order should the two
be given?

I'm thinking something like: bzr branch <remote> <local>
That makes sense.

But what about: bzr pull <remote>
It would be nice if you could specify local, so that you didn't have to
be in the directory to do an update. But if we make it

    bzr pull <remote> <local>

Then in order to update a local directory you have to give a remote
location. If you make it

    bzr pull <local> <remote>

Then you can updated a local directory easily, and if you are wanting to
create a new entry it's pretty easy to use "bzr pull . <remote>". The
only problem I have with it, is that you don't have the nice from->to
you actually have to <- from.

For my rpull/rpush code, I went with <local> <remote>, but I don't like
it a lot. It is especially clumsy, in that rpull can create a directory
if it doesn't exist. Effectively rpull acts just like branch if the
local directory doesn't exist.

I'm looking to do a "bzr missing" which also needs to know about a local
directory and a remote one. For now, I think I'll just leave it that the
local directory is always '.'.

The other possibility is to allow local to be supplied as an option,
rather than an argument. So you would do:
bzr missing --local=. <remote>
Is that resonable?

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050625/9184f699/attachment.pgp