Mercurial > hg
comparison help/extensions.txt @ 9539:c904e76e3834
help: move help topics from mercurial/help.py to help/*.txt
The help topics are loaded on demand so we wont hit the disk unless we
really have to.
author | Martin Geisler <mg@lazybytes.net> |
---|---|
date | Sun, 04 Oct 2009 09:59:13 +0200 |
parents | |
children | cad36e496640 |
comparison
equal
deleted
inserted
replaced
9538:f96ee862aba0 | 9539:c904e76e3834 |
---|---|
1 Mercurial has the ability to add new features through the use of | |
2 extensions. Extensions may add new commands, add options to | |
3 existing commands, change the default behavior of commands, or | |
4 implement hooks. | |
5 | |
6 Extensions are not loaded by default for a variety of reasons: | |
7 they can increase startup overhead; they may be meant for advanced | |
8 usage only; they may provide potentially dangerous abilities (such | |
9 as letting you destroy or modify history); they might not be ready | |
10 for prime time; or they may alter some usual behaviors of stock | |
11 Mercurial. It is thus up to the user to activate extensions as | |
12 needed. | |
13 | |
14 To enable the "foo" extension, either shipped with Mercurial or in | |
15 the Python search path, create an entry for it in your hgrc, like | |
16 this:: | |
17 | |
18 [extensions] | |
19 foo = | |
20 | |
21 You may also specify the full path to an extension:: | |
22 | |
23 [extensions] | |
24 myfeature = ~/.hgext/myfeature.py | |
25 | |
26 To explicitly disable an extension enabled in an hgrc of broader | |
27 scope, prepend its path with !:: | |
28 | |
29 [extensions] | |
30 # disabling extension bar residing in /path/to/extension/bar.py | |
31 hgext.bar = !/path/to/extension/bar.py | |
32 # ditto, but no path was supplied for extension baz | |
33 hgext.baz = ! |