Mercurial > hg
changeset 8782:d19ab9a56bf4
doc: wrap man pages after fixing quoting
| author | Martin Geisler <mg@lazybytes.net> |
|---|---|
| date | Thu, 11 Jun 2009 17:29:14 +0200 |
| parents | 385a2d94885e |
| children | 9154c79c67cc |
| files | doc/hgignore.5.txt doc/hgrc.5.txt |
| diffstat | 2 files changed, 37 insertions(+), 36 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/hgignore.5.txt Thu Jun 11 17:19:48 2009 +0200 +++ b/doc/hgignore.5.txt Thu Jun 11 17:29:14 2009 +0200 @@ -32,9 +32,9 @@ ------ An ignore file is a plain text file consisting of a list of patterns, -with one pattern per line. Empty lines are skipped. The "`#`" character -is treated as a comment character, and the "`\`" character is treated as -an escape character. +with one pattern per line. Empty lines are skipped. The "`#`" +character is treated as a comment character, and the "`\`" character +is treated as an escape character. Mercurial supports several pattern syntaxes. The default syntax used is Python/Perl-style regular expressions. @@ -54,9 +54,9 @@ follow, until another syntax is selected. Neither glob nor regexp patterns are rooted. A glob-syntax pattern of -the form "`*.c`" will match a file ending in "`.c`" in any directory, and -a regexp pattern of the form "`\.c$`" will do the same. To root a regexp -pattern, start it with "`^`". +the form "`*.c`" will match a file ending in "`.c`" in any directory, +and a regexp pattern of the form "`\.c$`" will do the same. To root a +regexp pattern, start it with "`^`". EXAMPLE -------
--- a/doc/hgrc.5.txt Thu Jun 11 17:19:48 2009 +0200 +++ b/doc/hgrc.5.txt Thu Jun 11 17:29:14 2009 +0200 @@ -19,9 +19,10 @@ Mercurial reads configuration data from several files, if they exist. The names of these files depend on the system on which Mercurial is -installed. `*.rc` files from a single directory are read in alphabetical -order, later ones overriding earlier ones. Where multiple paths are -given below, settings from later paths override earlier ones. +installed. `*.rc` files from a single directory are read in +alphabetical order, later ones overriding earlier ones. Where multiple +paths are given below, settings from later paths override earlier +ones. (Unix) `<install-root>/etc/mercurial/hgrc.d/*.rc`:: (Unix) `<install-root>/etc/mercurial/hgrc`:: @@ -48,8 +49,8 @@ which Mercurial is running. Options in these files apply to all Mercurial commands executed by any user in any directory. Registry keys contain PATH-like strings, every part of which must reference - a `Mercurial.ini` file or be a directory where `*.rc` files will be - read. + a `Mercurial.ini` file or be a directory where `*.rc` files will + be read. (Unix) `$HOME/.hgrc`:: (Windows) `%HOME%\Mercurial.ini`:: @@ -57,10 +58,10 @@ (Windows) `%USERPROFILE%\Mercurial.ini`:: (Windows) `%USERPROFILE%\.hgrc`:: Per-user configuration file(s), for the user running Mercurial. On - Windows 9x, `%HOME%` is replaced by `%APPDATA%`. - Options in these files apply to all Mercurial commands executed by - this user in any directory. Options in these files override - per-installation and per-system options. + Windows 9x, `%HOME%` is replaced by `%APPDATA%`. Options in these + files apply to all Mercurial commands executed by this user in any + directory. Options in these files override per-installation and + per-system options. (Unix, Windows) `<repo>/.hg/hgrc`:: Per-repository configuration options that only apply in a @@ -120,9 +121,9 @@ stable5 = latest -b stable -NOTE: It is possible to create aliases with the same names as -existing commands, which will then override the original definitions. -This is almost always a bad idea! +NOTE: It is possible to create aliases with the same names as existing +commands, which will then override the original definitions. This is +almost always a bad idea! -- [[auth]] @@ -144,10 +145,10 @@ Supported arguments: prefix;; - Either "++\*++" or a URI prefix with or without the scheme part. The - authentication entry with the longest matching prefix is used - (where "++*++" matches everything and counts as a match of length 1). - If the prefix doesn't include a scheme, the match is performed + Either "++\*++" or a URI prefix with or without the scheme part. + The authentication entry with the longest matching prefix is used + (where "++*++" matches everything and counts as a match of length + 1). If the prefix doesn't include a scheme, the match is performed against the URI with its scheme stripped as well, and the schemes argument, q.v., is then subsequently consulted. username;; @@ -176,14 +177,14 @@ Filters consist of a filter pattern followed by a filter command. Filter patterns are globs by default, rooted at the repository root. For example, to match any file ending in "`.txt`" in the root -directory only, use the pattern "++\*.txt++". To match any file ending in -"`.c`" anywhere in the repository, use the pattern "++**.c++". +directory only, use the pattern "++\*.txt++". To match any file ending +in "`.c`" anywhere in the repository, use the pattern "++**.c++". The filter command can start with a specifier, either "pipe:" or "tempfile:". If no specifier is given, "pipe:" is used by default. -A "pipe:" command must accept data on stdin and return the -transformed data on stdout. +A "pipe:" command must accept data on stdin and return the transformed +data on stdout. Pipe example: @@ -199,13 +200,13 @@ A "tempfile:" command is a template. The string INFILE is replaced with the name of a temporary file that contains the data to be -filtered by the command. The string OUTFILE is replaced with the -name of an empty temporary file, where the filtered data must be -written by the command. +filtered by the command. The string OUTFILE is replaced with the name +of an empty temporary file, where the filtered data must be written by +the command. -NOTE: the tempfile mechanism is recommended for Windows systems, -where the standard shell I/O redirection operators often have -strange effects and may corrupt the contents of your files. +NOTE: the tempfile mechanism is recommended for Windows systems, where +the standard shell I/O redirection operators often have strange +effects and may corrupt the contents of your files. The most common usage is for LF <-> CRLF translation on Windows. For this, use the "smart" converters which check for binary files: @@ -736,10 +737,10 @@ Warn if a `.hg/hgrc` file is ignored due to not being owned by a trusted user or group. True or False. Default is True. slash;; - Display paths using a slash ("++/++") as the path separator. This only - makes a difference on systems where the default path separator is - not the slash character (e.g. Windows uses the backslash character - ("++\++")). + Display paths using a slash ("++/++") as the path separator. This + only makes a difference on systems where the default path + separator is not the slash character (e.g. Windows uses the + backslash character ("++\++")). Default is False. ssh;; command to use for SSH connections. Default is 'ssh'.