best way to add unknowns from the command line?

[David Ingamells]

On 22/03/12 15:41, Wichmann, Mats D wrote:
>
>
> On Thu, Mar 22, 2012 at 8:21 AM, David Ingamells 
> <david.ingamells at mapscape.eu <mailto:david.ingamells at mapscape.eu>> wrote:
>
>     Since you seem to be using unix from your directory path syntax
>     why don't you write a little bit of bash - or python - or perl -
>     to loop over what bzr status returns and prompt before adding or
>     filter that list on a specific subdirectory?
>
>     Unix has a fantastic amount of tooling that works great together
>     but still people still seem to want every tool to re-invent every
>     wheel and do everything including wash the dishes.
>     I have to say that bzr isn't very unix friendly in this regard as
>     it doesn't have a command option that just lists the unknown files
>     without any spurious test.
>
>
> bzr ls -u   (aka: bzr ls --unknown)
>
I made a typo, but you probably understood:
s/spurious test/spurious text/

Thanks for the suggestion, bzr ls -u was new to me. However the 
behaviour of "bzr ls" is broken/confused in version 2.4.2. One would 
expect similar behaviour between "bzr ignored", "bzr ls --ignored" and 
"bzr --unknown" but:

    $ basename `pwd`
    trunk
    $ bzr ignored                # expect "trunk/distr"
    trunk/distr                                        ./trunk/distr
    $ bzr ls --ignored      # expect "distr/"
    $ bzr ls --unknown      # expect no output
    distr/

("bzr ignored" is showing correct behaviour).

Now if there were similar options/commands to also support all the other 
states reported by "bzr status"  it really would be great! Are there?

   added
   removed <-- probably not a option "bzr ls" can itself support.
   renamed
   modified
   kind changed
   unknown <-- this one buggily supported now
   ignored <-- this one buggily supported now

-- 

*David*