[PATCH] extensions: suggest --config extensions.bad=! when bad fails
timeless
timeless at gmail.com
Thu Sep 24 13:26:04 CDT 2015
On Tue, Sep 22, 2015 at 5:53 PM, Pierre-Yves David
<pierre-yves.david at ens-lyon.org> wrote:
> Not entirely enthousiastic about it. IF a user enable an extensions it
> should be able to disable it. But knowing that users are users, this is
> probably a bit too optimistic.
>
> However, temporary (--config) way to disable extensions is probably a bad
> sugguest in the "fail to import case" where there is low chance this will
> start importing again for the next run.
Depends. If something is automatically maintaining the extension (a
package manager, a VCS), then it might magically fix itself (this
happens to me often enough).
> Hi like Kevin proposal of listing all possible offender instead of the first
> one.
I'm not sure what you mean by "all possible offenders". Each thing
that fails to load gets its own line item, as shown in the test.
More information about the Mercurial-devel
mailing list