Comment 3 for bug 534603

The docs seem fine, as they describe the behaviour correctly. I'd like to see it changed in bzr, perhaps through the addition of a command line switch. I did manage to hack our scripts to (a) run the status command, (b) pushd to the source root, and (c) perform operations using the root-relative paths, so this is mostly resolved for me now. The only remaining issue is that it's now a bit of a pain to do something "custom" on-the-fly, like for example:

% rm `bzr status . -S | grep -e '^?' | awk '{print $2}'`

...to remove all non-versioned files in a directory. The above will fail, again because the paths reported are relative to some other dir.

Thanks.