This would set the configuration key named eggs to small. Lines beginning with # or are ignored and may be used to provide comments.Ĭonfiguration keys can be set multiple times, in which case Mercurial will use the value that was configured last. Leading whitespace is removed from values. If the lines that follow are indented, they are treated as continuations of that entry. SyntaxĪ configuration file consists of sections, led by a header and followed by name = value entries (sometimes called configuration keys): Įach line contains one entry. įor configs which should not be shared, should be used. On versions 5.7 and later, if share-safe functionality is enabled, shares will read config file of share source too. So far the directory only contains merge tool configuration but packagers can also put other default configuration there. Default configuration files should never be edited by users or administrators but can be overridden in other configuration files. The default configuration files are installed with Mercurial and will be overwritten on upgrades. Mercurial comes with some default configuration. Options in these files override per-installation options. Options in these files apply to all Mercurial commands executed by any user in any directory. Per-system configuration files are for the system on which Mercurial is running. Mercurial checks each of these locations in the specified order until one or more configuration files are detected. 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. Per-installation configuration files are for the system on which Mercurial is running. is the parent directory of the hg executable (or symlink) being run.įor example, if installed in /shared/tools/bin/hg, Mercurial will look in /shared/tools/etc/mercurial/hgrc. Per-installation configuration files are searched for in the directory where Mercurial is installed. Options in these files override per-system and per-installation options. Options in these files apply to all Mercurial commands executed by this user in any directory. Per-user configuration file(s) are for the user running Mercurial. On Plan 9 and Unix, most of this file will be ignored if it doesn't belong to a trusted user or to a trusted group. Options in this file override options in all other configuration files. This file is not version-controlled, and will not get transferred during a "clone" operation. Per-repository configuration options only apply in a particular repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |