# HG changeset patch
# User Cédric Duval <cedricduval@free.fr>
# Date 2009-06-20 18:57:13
# Node ID 87c30fb7e8dffb5c08e967aaad5548539162d250
# Parent  37d8a5ddd4991e116686ddf6cb86db7aa4db487c

help: remove per-extension paragraph on how to enable it

The central place to find this information is the "extensions" help topic.

diff --git a/hgext/color.py b/hgext/color.py
--- a/hgext/color.py
+++ b/hgext/color.py
@@ -29,10 +29,6 @@ also available. Effects are rendered wit
 function (aka ANSI escape codes). This module also provides the
 render_text function, which can be used to add effects to any text.
 
-To enable this extension, add this to your .hgrc file:
-[extensions]
-color =
-
 Default effects may be overridden from the .hgrc file:
 
 [color]
diff --git a/hgext/extdiff.py b/hgext/extdiff.py
--- a/hgext/extdiff.py
+++ b/hgext/extdiff.py
@@ -12,11 +12,6 @@ programs are called with a configurable 
 non-option arguments: paths to directories containing snapshots of
 files to compare.
 
-To enable this extension:
-
-  [extensions]
-  hgext.extdiff =
-
 The `extdiff' extension also allows to configure new diff commands, so
 you do not need to type "hg extdiff -p kdiff3" always.
 
diff --git a/hgext/hgk.py b/hgext/hgk.py
--- a/hgext/hgk.py
+++ b/hgext/hgk.py
@@ -14,20 +14,8 @@ distributed with Mercurial.)
 hgk consists of two parts: a Tcl script that does the displaying and
 querying of information, and an extension to Mercurial named hgk.py,
 which provides hooks for hgk to get information. hgk can be found in
-the contrib directory, and hgk.py can be found in the hgext directory.
-
-To load the hgext.py extension, add it to your .hgrc file (you have to
-use your global $HOME/.hgrc file, not one in a repository). You can
-specify an absolute path:
-
-  [extensions]
-  hgk=/usr/local/lib/hgk.py
-
-Mercurial can also scan the default python library path for a file
-named 'hgk.py' if you set hgk empty:
-
-  [extensions]
-  hgk=
+the contrib directory, and the extension is shipped in the hgext
+repository, and needs to be enabled.
 
 The hg view command will launch the hgk Tcl script. For this command
 to work, hgk must be in your search path. Alternately, you can specify
diff --git a/hgext/highlight/__init__.py b/hgext/highlight/__init__.py
--- a/hgext/highlight/__init__.py
+++ b/hgext/highlight/__init__.py
@@ -13,11 +13,6 @@
 It depends on the Pygments syntax highlighting library:
 http://pygments.org/
 
-To enable the extension add this to hgrc:
-
-[extensions]
-hgext.highlight =
-
 There is a single configuration option:
 
 [web]
diff --git a/hgext/interhg.py b/hgext/interhg.py
--- a/hgext/interhg.py
+++ b/hgext/interhg.py
@@ -14,12 +14,8 @@ This extension allows the use of a speci
 which will be automatically expanded into links or any other
 arbitrary expression, much like InterWiki does.
 
-To enable this extension, add the following lines to your hgrc:
-
-  [extensions]
-  interhg =
-
-A few example patterns (link to bug tracking, etc.):
+A few example patterns (link to bug tracking, etc.) that may
+be used in your hgrc:
 
   [interhg]
   issues = s!issue(\d+)!<a href="http://bts/issue\1">issue\1<\/a>!
diff --git a/hgext/keyword.py b/hgext/keyword.py
--- a/hgext/keyword.py
+++ b/hgext/keyword.py
@@ -21,12 +21,6 @@
 #
 # Binary files are not touched.
 #
-# Setup in hgrc:
-#
-#   [extensions]
-#   # enable extension
-#   hgext.keyword =
-#
 # Files to act upon/ignore are specified in the [keyword] section.
 # Customized keyword template mappings in the [keywordmaps] section.
 #
diff --git a/hgext/patchbomb.py b/hgext/patchbomb.py
--- a/hgext/patchbomb.py
+++ b/hgext/patchbomb.py
@@ -28,11 +28,6 @@ With the -d/--diffstat option, you will 
 with a diffstat summary and the changeset summary, so you can be sure
 you are sending the right changes.
 
-To enable this extension:
-
-  [extensions]
-  hgext.patchbomb =
-
 To configure other defaults, add a section like this to your hgrc
 file:
 
diff --git a/hgext/purge.py b/hgext/purge.py
--- a/hgext/purge.py
+++ b/hgext/purge.py
@@ -6,10 +6,6 @@
 # This program was inspired by the "cvspurge" script contained in CVS utilities
 # (http://www.red-bean.com/cvsutils/).
 #
-# To enable the "purge" extension put these lines in your ~/.hgrc:
-#  [extensions]
-#  hgext.purge =
-#
 # For help on the usage of "hg purge" use:
 #  hg help purge
 #
diff --git a/hgext/win32mbcs.py b/hgext/win32mbcs.py
--- a/hgext/win32mbcs.py
+++ b/hgext/win32mbcs.py
@@ -33,11 +33,6 @@ Note that there are some limitations on 
  * You should set same encoding for the repository by locale or
    HGENCODING.
 
-To use this extension, enable the extension in .hg/hgrc or ~/.hgrc:
-
-  [extensions]
-  hgext.win32mbcs =
-
 Path encoding conversion are done between Unicode and
 encoding.encoding which is decided by Mercurial from current locale
 setting or HGENCODING.
diff --git a/hgext/zeroconf/__init__.py b/hgext/zeroconf/__init__.py
--- a/hgext/zeroconf/__init__.py
+++ b/hgext/zeroconf/__init__.py
@@ -11,12 +11,6 @@ Zeroconf enabled repositories will be an
 the need to configure a server or a service. They can be discovered
 without knowing their actual IP address.
 
-To use the zeroconf extension add the following entry to your hgrc
-file:
-
-[extensions]
-hgext.zeroconf =
-
 To allow other people to discover your repository using run "hg serve"
 in your repository.