[PATCH 2 of 2] extensions: suggest --config extensions.bad=! when bad fails

[timeless]

Augie Fackler wrote:
> > +  (you can use '--config extensions.badext=!$TESTTMP/badext.py' to
disable it)
>
> is specifying the path to the extension needed here? can't it just be
> extensions.badext=! ?

I haven't worked through the logic, I think there's some value in
discovering this feature, but it's possible that a simple "!" is enough.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20150915/69d13933/attachment.html>