Improve messaging for bzr add into branch w/o a working tree

[John Whitley]

Peter Amstutz on the bzr mailing list gave this confusing example, reported on bzr 0.8:

$ bzr init-repo bzrbug

$ cd bzrbug/

$ ls

$ bzr init foo

$ cd foo

$ touch bar

$ bzr add bar
bzr: ERROR: No WorkingTree exists for /home/tetron/hack/mine/bzrbug/foo/.bzr/checkout/.

The mistake was that "bzr init-repo" needed the --trees option to allow branches in the repository to have working trees. The messaging is rather unhelpful, and provides an inexperienced user with little information with which to understand or rectify the problem.

[John A Meinel (jameinel)]

I believe the proposed fix is to change the default value of 'bzr init-repo' to include --trees. (rather than being --no-trees).

Alternatively, maybe we could make the default be based on whether the target location is local or remote.

Either way, this has probably gotten a little bit worse, because of the URL and encoding fixes, they now get a URL:
liliana % bzr add foo
bzr: ERROR: No WorkingTree exists for file:///home/jameinel/dev/bzr/%2Ctmp/c/xxyy/.bzr/checkout/.

[John A Meinel (jameinel)]

This still hasn't been done, I'll try to bring it up on the list

[John A Meinel (jameinel)]

Switching the default to --trees should be done for bzr-0.13

[John A Meinel (jameinel)]

The switch to --trees was released in bzr-0.15rc2