comparison hgext/hgk.py @ 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 bf17aeafb869
children 868670dbc237
comparison
equal deleted inserted replaced
8865:37d8a5ddd499 8866:87c30fb7e8df
12 distributed with Mercurial.) 12 distributed with Mercurial.)
13 13
14 hgk consists of two parts: a Tcl script that does the displaying and 14 hgk consists of two parts: a Tcl script that does the displaying and
15 querying of information, and an extension to Mercurial named hgk.py, 15 querying of information, and an extension to Mercurial named hgk.py,
16 which provides hooks for hgk to get information. hgk can be found in 16 which provides hooks for hgk to get information. hgk can be found in
17 the contrib directory, and hgk.py can be found in the hgext directory. 17 the contrib directory, and the extension is shipped in the hgext
18 18 repository, and needs to be enabled.
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=
31 19
32 The hg view command will launch the hgk Tcl script. For this command 20 The hg view command will launch the hgk Tcl script. For this command
33 to work, hgk must be in your search path. Alternately, you can specify 21 to work, hgk must be in your search path. Alternately, you can specify
34 the path to hgk in your .hgrc file: 22 the path to hgk in your .hgrc file:
35 23