[BUG] --state used when it shouldn't be

[Andy Armstrong]

On 4 Jan 2008, at 16:15, Ovid wrote:
> --- Andy Armstrong <andy at hexten.net> wrote:
>
>> So I guess I'm saying I don't know what .proverc is for :/
>
> Well, I think I had envisioned it as something which would be used if
> prove was run with no arguments.  I'd then be creating custom .proverc
> files on a per-project basis, depending on what my needs were, but if
> any arguments at all were supplied, than prove would assume you knew
> what you were doing.  However, I am constantly finding myself pushing
> the boundaries of what I need from tests and that changes my needs.
>
> That being said, if it causes more trouble than it's worth, I can see
> not using it and will cheerfully concede that it was a bad idea :)


I don't think it's too late to change or deprecate it. I doubt too  
many people are using it yet.

If .proverc is only used when prove has no args it means that

$ prove

can only ever have one meaning until you edit .proverc. I think that  
limits its utility.

I'm probably not a great source of .proverc use cases though - I tend  
to hit ^R in bash and reverse search for a recent prove incantation  
that I like :)

-- 
Andy Armstrong, Hexten