Bazaar Explorer question

[Ian Clatworthy]

Russel Winder wrote:
> Whenever I start "bzr explorer" I always get the "no working tree".  If
> I start this in a directory which is not a branch or a shared repository
> then that seems fine.  However if I start "bzr explorer" in a branch or
> shared repository my expectation is that it would automatically open
> that branch or repository -- though maybe it cannot deal with
> repositories?

FWIW, I usually start with "bzr explorer ." when launching from the
command line.

> Given that all other bzr operations work on the branch that is the
> current directory, this behaviour of the explorer command does seem
> slightly out of idiom.

There is a slight difference in expectation though. If a bzr command is
run outside of a sensible place, it tends to immediately fall over and
error out. In contrast, most users expect a GUI application to start-up
and then let you select the document/project you're working on. That's
particularly true when launching from the Applications/Start menu or
from a shortcut in your "quick-launch bar", which is where we want to
get to.

So that's why it's the way it is. I'll accept a patch to change it
though. It would need to behave as follows I think:

  bzr explorer foo - error dialog if foo isn't a bzr location
  bzr explorer - open current directory iff it's a bzr location

Sound right?

Ian C.