![]() Only used if the prefix doesn't include a scheme. Space separated list of URI schemes to use this authentication entry with. PEM encoded client certificate chain file. PEM encoded client certificate key file.Ĭert Optional. If not given, and the remote site requires basic or digest authentication, the user will be prompted for If the prefix doesn't include a scheme, the match is performed against the URI with its scheme stripped as well,Īnd the schemes argument, q.v., is then subsequently consulted. The authentication entry with the longest matching prefix is used (where * matchesĮverything and counts as a match of length 1). Prefix Either * or a URI prefix with or without the scheme part. = where is used to group arguments into authentication entries. Aliases allow you to define your own commands in terms of other commands (or aliases), optionally including arguments.Īlias definitions consist of lines of the form: This section describes the different sections that may appear in a Mercurial "hgrc" file, the purpose of each section, its possible keys, and their possibleĪlias Defines command aliases. Filenames are relative to the configuration file in which the %include directive is found.Ī line with %unset name will remove name from the current section, if it has been set previously. The inclusion is recursive, which means that includedįiles can include other files. Lines beginning with # or are ignored and may be used to provide comments.Ī line of the form %include file will include file into the current configuration file. If the lines that follow are indented, they are treated as continuations of that entry. Registry keys contain PATH-like strings, every part of which must reference a Mercurial.ini file or be a directory whereĪ configuration file consists of sections, led by a header and followed by name = value entries:ĮggsEach line contains one entry. ![]() Options in these files apply to all Mercurial commands executedīy any user in any directory. Per-installation/system configuration files, for the system on which Mercurial is running. (Windows) HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial Options in these files apply to all Mercurial commands executed by any user in any directory. For example, if installed in /shared/tools/bin/hg, Mercurial will look in Per-installation configuration files, searched for in the directory where Mercurial is installed. Options in these files override per-installation options. Options in these files apply to all Mercurial commands executed by any user inĪny directory. Per-system configuration files, for the system on which Mercurial is running. Options in these files override per-system and per-installation options. To all Mercurial commands executed by this user in any directory. ![]() On Windows 9x, %HOME% is replaced by %APPDATA%. Per-user configuration file(s), for the user running Mercurial. See the documentation for the trusted section below for more details. ![]() On Unix, most of this file will be ignored if it doesn't belong to a Options in this file override options in all other configuration files. This file is not version-controlled, and will not get transferred during a Per-repository configuration options that only apply in a particular repository. Where multiple paths are given below, settings *.rc files from a single directory are read in alphabetical order, later ones overriding earlier ones. The names of these files depend on the system on which Mercurial is installed. Mercurial reads configuration data from several files, if they exist. The Mercurial system uses a set of configuration files to control aspects of its behavior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |