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