default scope of different bzr commands

[Martin Pool]

On Fri, Nov 7, 2008 at 8:59 AM, Kuno Meyer <kuno.meyer at gmx.ch> wrote:
> Hi all
>
> Is there a specific reason, why the default scope of the "bzr add" command
> is "." (e.g. "bzr add" is equivalent to "bzr add ."), whereas for most of
> the other working tree related commands (like "bzr st", "bzr diff", "bzr
> ignore", "bzr revert", ...), it is the branch root? Even "bzr ignored"
> operates on the whole branch, whereas "bzr ls" assumes ".".
>
> This inconsistency is quite confusing to me, leading to occasional usage
> errors of the type of "more/less work done than expected". I'd prefer to
> have an identical default scope for all commands, possibly the branch root.

There is no specific reason.  We'd like someone to change it so that
paths are always printed relative to the cwd, and operations are
across the whole tree unless a path is given.

> In addition, I wanted to mention that I was quite surprised today to see
>  that "bzr add" seemingly ignores .bzrignore:
>
>        mkdir a; touch a\b
>        bzr init; bzr ignore a
>        cd a
>        bzr add
>
> (... well, the behaviour can be seen as correct according to the
> documentation, but nevertheless ...)

I think this follows from the above: it's implicitly "bzr add ." and
adding a directory or file overrides it being ignored.  I agree it is
a bit confusing.

-- 
Martin <http://launchpad.net/~mbp/>