Show More
@@ -32,9 +32,9 b' SYNTAX' | |||
|
32 | 32 | ------ |
|
33 | 33 | |
|
34 | 34 | An ignore file is a plain text file consisting of a list of patterns, |
|
35 |
with one pattern per line. Empty lines are skipped. The "`#`" |
|
|
36 |
is treated as a comment character, and the "`\`" character |
|
|
37 | an escape character. | |
|
35 | with one pattern per line. Empty lines are skipped. The "`#`" | |
|
36 | character is treated as a comment character, and the "`\`" character | |
|
37 | is treated as an escape character. | |
|
38 | 38 | |
|
39 | 39 | Mercurial supports several pattern syntaxes. The default syntax used |
|
40 | 40 | is Python/Perl-style regular expressions. |
@@ -54,9 +54,9 b' The chosen syntax stays in effect when p' | |||
|
54 | 54 | follow, until another syntax is selected. |
|
55 | 55 | |
|
56 | 56 | Neither glob nor regexp patterns are rooted. A glob-syntax pattern of |
|
57 |
the form "`*.c`" will match a file ending in "`.c`" in any directory, |
|
|
58 |
a regexp pattern of the form "`\.c$`" will do the same. To root a |
|
|
59 | pattern, start it with "`^`". | |
|
57 | the form "`*.c`" will match a file ending in "`.c`" in any directory, | |
|
58 | and a regexp pattern of the form "`\.c$`" will do the same. To root a | |
|
59 | regexp pattern, start it with "`^`". | |
|
60 | 60 | |
|
61 | 61 | EXAMPLE |
|
62 | 62 | ------- |
@@ -19,9 +19,10 b' FILES' | |||
|
19 | 19 | |
|
20 | 20 | Mercurial reads configuration data from several files, if they exist. |
|
21 | 21 | The names of these files depend on the system on which Mercurial is |
|
22 |
installed. `*.rc` files from a single directory are read in |
|
|
23 |
order, later ones overriding earlier ones. Where multiple |
|
|
24 |
given below, settings from later paths override earlier |
|
|
22 | installed. `*.rc` files from a single directory are read in | |
|
23 | alphabetical order, later ones overriding earlier ones. Where multiple | |
|
24 | paths are given below, settings from later paths override earlier | |
|
25 | ones. | |
|
25 | 26 | |
|
26 | 27 | (Unix) `<install-root>/etc/mercurial/hgrc.d/*.rc`:: |
|
27 | 28 | (Unix) `<install-root>/etc/mercurial/hgrc`:: |
@@ -48,8 +49,8 b' given below, settings from later paths o' | |||
|
48 | 49 | which Mercurial is running. Options in these files apply to all |
|
49 | 50 | Mercurial commands executed by any user in any directory. Registry |
|
50 | 51 | keys contain PATH-like strings, every part of which must reference |
|
51 |
a `Mercurial.ini` file or be a directory where `*.rc` files will |
|
|
52 | read. | |
|
52 | a `Mercurial.ini` file or be a directory where `*.rc` files will | |
|
53 | be read. | |
|
53 | 54 | |
|
54 | 55 | (Unix) `$HOME/.hgrc`:: |
|
55 | 56 | (Windows) `%HOME%\Mercurial.ini`:: |
@@ -57,10 +58,10 b' given below, settings from later paths o' | |||
|
57 | 58 | (Windows) `%USERPROFILE%\Mercurial.ini`:: |
|
58 | 59 | (Windows) `%USERPROFILE%\.hgrc`:: |
|
59 | 60 | Per-user configuration file(s), for the user running Mercurial. On |
|
60 | Windows 9x, `%HOME%` is replaced by `%APPDATA%`. | |
|
61 |
|
|
|
62 |
|
|
|
63 |
per- |
|
|
61 | Windows 9x, `%HOME%` is replaced by `%APPDATA%`. Options in these | |
|
62 | files apply to all Mercurial commands executed by this user in any | |
|
63 | directory. Options in these files override per-installation and | |
|
64 | per-system options. | |
|
64 | 65 | |
|
65 | 66 | (Unix, Windows) `<repo>/.hg/hgrc`:: |
|
66 | 67 | Per-repository configuration options that only apply in a |
@@ -120,9 +121,9 b' changesets. You can define subsequent al' | |||
|
120 | 121 | |
|
121 | 122 | stable5 = latest -b stable |
|
122 | 123 | |
|
123 | NOTE: It is possible to create aliases with the same names as | |
|
124 |
|
|
|
125 |
|
|
|
124 | NOTE: It is possible to create aliases with the same names as existing | |
|
125 | commands, which will then override the original definitions. This is | |
|
126 | almost always a bad idea! | |
|
126 | 127 | -- |
|
127 | 128 | |
|
128 | 129 | [[auth]] |
@@ -144,10 +145,10 b' Example:' | |||
|
144 | 145 | Supported arguments: |
|
145 | 146 | |
|
146 | 147 | prefix;; |
|
147 |
Either "++\*++" or a URI prefix with or without the scheme part. |
|
|
148 | authentication entry with the longest matching prefix is used | |
|
149 |
(where "++*++" matches everything and counts as a match of length |
|
|
150 | If the prefix doesn't include a scheme, the match is performed | |
|
148 | Either "++\*++" or a URI prefix with or without the scheme part. | |
|
149 | The authentication entry with the longest matching prefix is used | |
|
150 | (where "++*++" matches everything and counts as a match of length | |
|
151 | 1). If the prefix doesn't include a scheme, the match is performed | |
|
151 | 152 | against the URI with its scheme stripped as well, and the schemes |
|
152 | 153 | argument, q.v., is then subsequently consulted. |
|
153 | 154 | username;; |
@@ -176,14 +177,14 b' decode/encode::' | |||
|
176 | 177 | Filters consist of a filter pattern followed by a filter command. |
|
177 | 178 | Filter patterns are globs by default, rooted at the repository root. |
|
178 | 179 | For example, to match any file ending in "`.txt`" in the root |
|
179 |
directory only, use the pattern "++\*.txt++". To match any file ending |
|
|
180 | "`.c`" anywhere in the repository, use the pattern "++**.c++". | |
|
180 | directory only, use the pattern "++\*.txt++". To match any file ending | |
|
181 | in "`.c`" anywhere in the repository, use the pattern "++**.c++". | |
|
181 | 182 | |
|
182 | 183 | The filter command can start with a specifier, either "pipe:" or |
|
183 | 184 | "tempfile:". If no specifier is given, "pipe:" is used by default. |
|
184 | 185 | |
|
185 | A "pipe:" command must accept data on stdin and return the | |
|
186 |
|
|
|
186 | A "pipe:" command must accept data on stdin and return the transformed | |
|
187 | data on stdout. | |
|
187 | 188 | |
|
188 | 189 | Pipe example: |
|
189 | 190 | |
@@ -199,13 +200,13 b' Pipe example:' | |||
|
199 | 200 | |
|
200 | 201 | A "tempfile:" command is a template. The string INFILE is replaced |
|
201 | 202 | with the name of a temporary file that contains the data to be |
|
202 | filtered by the command. The string OUTFILE is replaced with the | |
|
203 |
|
|
|
204 |
|
|
|
203 | filtered by the command. The string OUTFILE is replaced with the name | |
|
204 | of an empty temporary file, where the filtered data must be written by | |
|
205 | the command. | |
|
205 | 206 | |
|
206 | NOTE: the tempfile mechanism is recommended for Windows systems, | |
|
207 |
|
|
|
208 |
|
|
|
207 | NOTE: the tempfile mechanism is recommended for Windows systems, where | |
|
208 | the standard shell I/O redirection operators often have strange | |
|
209 | effects and may corrupt the contents of your files. | |
|
209 | 210 | |
|
210 | 211 | The most common usage is for LF <-> CRLF translation on Windows. For |
|
211 | 212 | this, use the "smart" converters which check for binary files: |
@@ -736,10 +737,10 b' merge-tools section.' | |||
|
736 | 737 | Warn if a `.hg/hgrc` file is ignored due to not being owned by a |
|
737 | 738 | trusted user or group. True or False. Default is True. |
|
738 | 739 | slash;; |
|
739 |
Display paths using a slash ("++/++") as the path separator. This |
|
|
740 |
makes a difference on systems where the default path |
|
|
741 |
not the slash character (e.g. Windows uses the |
|
|
742 | ("++\++")). | |
|
740 | Display paths using a slash ("++/++") as the path separator. This | |
|
741 | only makes a difference on systems where the default path | |
|
742 | separator is not the slash character (e.g. Windows uses the | |
|
743 | backslash character ("++\++")). | |
|
743 | 744 | Default is False. |
|
744 | 745 | ssh;; |
|
745 | 746 | command to use for SSH connections. Default is 'ssh'. |
General Comments 0
You need to be logged in to leave comments.
Login now