[PATCH] Allow explicit disabling of extensions

Steve Borho steve at borho.org
Tue Sep 18 22:04:47 CDT 2007

On Wed, 2007-09-19 at 03:19 +0100, TK Soh wrote:
> On 9/19/07, Steve Borho <steve at borho.org> wrote:
> > # HG changeset patch
> > # User Steve Borho <steve at borho.org>
> > # Date 1190163181 18000
> > # Node ID 98203cff47ce85df26094d03eda8c79ab858f2e2
> > # Parent  ba3dc78839686ccb285f4227a80356f7b13e6f8f
> > Allow explicit disabling of extensions
> >
> > If the first character of an extension path is '!', the extension
> > is silently skipped.
> Just wondering, what happen to simply commenting out the extension entry?

I described three use cases in my e-mail this morning, but there's
basically two main reasons why this is useful:

* There's no other way to override a system-wide extension (if your
sysadmin enabled an extension in /etc/hgrc, there's currently no way to
disable it).

* For the purposes of libraries that read/write INI files, there's no
difference between commenting out a line and completely removing it.
Comments in the files are typically maintained so they aren't harmed by
update operations, but they are never parsed (for good reason) and these
libraries do not provide functionality for (un)commenting lines.

If there's a better way to mark an extension as disabled, I'd be happy
to hear it.  This seemed like the least intrusive solution.


Steve Borho (steve at borho.org)
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292 F2C6 2C8C

More information about the Mercurial-devel mailing list