Mercurial > hg
changeset 8866:87c30fb7e8df
help: remove per-extension paragraph on how to enable it
The central place to find this information is the "extensions" help topic.
| author | Cédric Duval <cedricduval@free.fr> |
|---|---|
| date | Sat, 20 Jun 2009 20:57:13 +0200 |
| parents | 37d8a5ddd499 |
| children | ff817723280a |
| files | hgext/color.py hgext/extdiff.py hgext/hgk.py hgext/highlight/__init__.py hgext/interhg.py hgext/keyword.py hgext/patchbomb.py hgext/purge.py hgext/win32mbcs.py hgext/zeroconf/__init__.py |
| diffstat | 10 files changed, 4 insertions(+), 60 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/color.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/color.py Sat Jun 20 20:57:13 2009 +0200 @@ -29,10 +29,6 @@ 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]
--- a/hgext/extdiff.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/extdiff.py Sat Jun 20 20:57:13 2009 +0200 @@ -12,11 +12,6 @@ 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.
--- a/hgext/hgk.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/hgk.py Sat Jun 20 20:57:13 2009 +0200 @@ -14,20 +14,8 @@ 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
--- a/hgext/highlight/__init__.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/highlight/__init__.py Sat Jun 20 20:57:13 2009 +0200 @@ -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]
--- a/hgext/interhg.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/interhg.py Sat Jun 20 20:57:13 2009 +0200 @@ -14,12 +14,8 @@ 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>!
--- a/hgext/keyword.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/keyword.py Sat Jun 20 20:57:13 2009 +0200 @@ -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. #
--- a/hgext/patchbomb.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/patchbomb.py Sat Jun 20 20:57:13 2009 +0200 @@ -28,11 +28,6 @@ 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:
--- a/hgext/purge.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/purge.py Sat Jun 20 20:57:13 2009 +0200 @@ -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 #
--- a/hgext/win32mbcs.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/win32mbcs.py Sat Jun 20 20:57:13 2009 +0200 @@ -33,11 +33,6 @@ * 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.
--- a/hgext/zeroconf/__init__.py Sat Jun 20 20:55:50 2009 +0200 +++ b/hgext/zeroconf/__init__.py Sat Jun 20 20:57:13 2009 +0200 @@ -11,12 +11,6 @@ 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.