##// END OF EJS Templates
help: expand the extensions topic
Cédric Duval -
r8865:37d8a5dd default
parent child Browse files
Show More
@@ -127,13 +127,37 b' def extensionslisting(header, exts, maxl'
127 127
128 128 def topicextensions():
129 129 doc = _(r'''
130 Mercurial has an extension mechanism for adding new features.
130 Mercurial has a mechanism for adding new features through the
131 use of extensions. Extensions may bring new commands, or new
132 hooks, or change some behaviors of Mercurial.
133
134 Extensions are not loaded by default for a variety of reasons,
135 they may be meant for an advanced usage or provide potentially
136 dangerous commands (eg. mq or rebase allow to rewrite history),
137 they might not be yet ready for prime-time, or they may alter
138 some usual behaviors of stock Mercurial. It is thus up to the
139 user to activate the extensions as needed.
140
141 To enable an extension "foo" which is either shipped with
142 Mercurial or in the Python search path, create an entry for
143 it in your hgrc, like this:
131 144
132 To enable an extension "foo" bundled with Mercurial, create an
133 entry for it your hgrc, like this:
134
135 [extensions]
136 foo =
145 [extensions]
146 foo =
147
148 You may also specify the full path where an extension resides:
149
150 [extensions]
151 myfeature = ~/.hgext/myfeature.py
152
153 To explicitly disable an extension which is enabled in an hgrc
154 of broader scope, prepend its path with !:
155
156 [extensions]
157 # disabling extension bar residing in /ext/path
158 hgext.bar = !/path/to/extension/bar.py
159 # ditto, but no path was supplied for extension baz
160 hgext.baz = !
137 161 ''')
138 162
139 163 exts, maxlength = enabledextensions()
General Comments 0
You need to be logged in to leave comments. Login now