The Mercurial system uses a set of configuration files to control
aspects of its behavior.
The configuration files use a simple ini-file format. A configuration
file consists of sections, led by a ``[section]`` header and followed
by ``name = value`` entries::
[ui]
username = Firstname Lastname <firstname.lastname@example.net>
verbose = True
The above entries will be referred to as ``ui.username`` and
``ui.verbose``, respectively. See the Syntax section below.
Files
-----
Mercurial reads configuration data from several files, if they exist.
These files do not exist by default and you will have to create the
appropriate configuration files yourself: global configuration like
the username setting is typically put into
``%USERPROFILE%\mercurial.ini`` or ``$HOME/.hgrc`` and local
configuration is put into the per-repository ``<repo>/.hg/hgrc`` file.
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 earlier paths override later
ones.
| (Unix, Windows) ``<repo>/.hg/hgrc``
Per-repository configuration options that only apply in a
particular repository. This file is not version-controlled, and
will not get transferred during a "clone" operation. Options in
this file override options in all other configuration files. On
Unix, most of this file will be ignored if it doesn't belong to a
trusted user or to a trusted group. See the documentation for the
``[trusted]`` section below for more details.
| (Unix) ``$HOME/.hgrc``
| (Windows) ``%USERPROFILE%\.hgrc``
| (Windows) ``%USERPROFILE%\Mercurial.ini``
| (Windows) ``%HOME%\.hgrc``
| (Windows) ``%HOME%\Mercurial.ini``
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-system and per-installation
options.
| (Unix) ``/etc/mercurial/hgrc``
| (Unix) ``/etc/mercurial/hgrc.d/*.rc``
Per-system configuration files, for the system on which Mercurial
is running. Options in these files apply to all Mercurial commands
executed by any user in any directory. Options in these files
override per-installation options.
| (Unix) ``<install-root>/etc/mercurial/hgrc``
| (Unix) ``<install-root>/etc/mercurial/hgrc.d/*.rc``
Per-installation configuration files, searched for in the
directory where Mercurial is installed. ``<install-root>`` is the
parent directory of the **hg** executable (or symlink) being run. For
example, if installed in ``/shared/tools/bin/hg``, Mercurial will look
in ``/shared/tools/etc/mercurial/hgrc``. Options in these files apply
to all Mercurial commands executed by any user in any directory.
| (Windows) ``<install-dir>\Mercurial.ini`` **or**
| (Windows) ``<install-dir>\hgrc.d\*.rc`` **or**
| (Windows) ``HKEY_LOCAL_MACHINE\SOFTWARE\Mercurial``
Per-installation/system configuration files, for the system on
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. Mercurial checks each of these locations in the specified
order until one or more configuration files are detected. If the
pywin32 extensions are not installed, Mercurial will only look for
site-wide configuration in ``C:\Mercurial\Mercurial.ini``.
Syntax
------
A configuration file consists of sections, led by a ``[section]`` header
and followed by ``name = value`` entries (sometimes called
``configuration keys``)::
[spam]
eggs=ham
green=
eggs
Each line contains one entry. If the lines that follow are indented,
they are treated as continuations of that entry. Leading whitespace is
removed from values. Empty lines are skipped. Lines beginning with
``#`` or ``;`` are ignored and may be used to provide comments.
Configuration keys can be set multiple times, in which case Mercurial
will use the value that was configured last. As an example::
[spam]
eggs=large
ham=serrano
eggs=small
This would set the configuration key named ``eggs`` to ``small``.
It is also possible to define a section multiple times. A section can
be redefined on the same and/or on different configuration files. For
example::
[foo]
eggs=large
ham=serrano
eggs=small
[bar]
eggs=ham
green=
eggs
[foo]
ham=prosciutto
eggs=medium
bread=toasted
This would set the ``eggs``, ``ham``, and ``bread`` configuration keys
of the ``foo`` section to ``medium``, ``prosciutto``, and ``toasted``,
respectively. As you can see there only thing that matters is the last
value that was set for each of the configuration keys.
If a configuration key is set multiple times in different
configuration files the final value will depend on the order in which
the different configuration files are read, with settings from earlier
paths overriding later ones as described on the ``Files`` section
above.
A line of the form ``%include file`` will include ``file`` into the
current configuration file. The inclusion is recursive, which means
that included files can include other files. Filenames are relative to
the configuration file in which the ``%include`` directive is found.
Environment variables and ``~user`` constructs are expanded in
``file``. This lets you do something like::
%include ~/.hgrc.d/$HOST.rc
to include a different configuration file on each computer you use.
A line with ``%unset name`` will remove ``name`` from the current
section, if it has been set previously.
The values are either free-form text strings, lists of text strings,
or Boolean values. Boolean values can be set to true using any of "1",
"yes", "true", or "on" and to false using "0", "no", "false", or "off"
(all case insensitive).
List values are separated by whitespace or comma, except when values are
placed in double quotation marks::
allow_read = "John Doe, PhD", brian, betty
Quotation marks can be escaped by prefixing them with a backslash. Only
quotation marks at the beginning of a word is counted as a quotation
(e.g., ``foo"bar baz`` is the list of ``foo"bar`` and ``baz``).
Sections
--------
This section describes the different sections that may appear in a
Mercurial configuration file, the purpose of each section, its possible
keys, and their possible values.
``alias``
"""""""""
Defines command aliases.
Aliases allow you to define your own commands in terms of other
commands (or aliases), optionally including arguments. Positional
arguments in the form of ``$1``, ``$2``, etc in the alias definition
are expanded by Mercurial before execution. Positional arguments not
already used by ``$N`` in the definition are put at the end of the
command to be executed.
Alias definitions consist of lines of the form::
<alias> = <command> [<argument>]...
For example, this definition::
latest = log --limit 5
creates a new command ``latest`` that shows only the five most recent
changesets. You can define subsequent aliases using earlier ones::
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!
An alias can start with an exclamation point (``!``) to make it a
shell alias. A shell alias is executed with the shell and will let you
run arbitrary commands. As an example, ::
echo = !echo
will let you do ``hg echo foo`` to have ``foo`` printed in your
terminal. A better example might be::
purge = !$HG status --no-status --unknown -0 | xarg
没有合适的资源?快使用搜索试试~ 我知道了~
Arctic Core是AUTOSAR标准开放源码(GPL)的嵌入式系统平台
共2000个文件
png:943个
gif:452个
htm:277个
需积分: 5 10 下载量 70 浏览量
2022-10-24
20:24:09
上传
评论 3
收藏 144.86MB ZIP 举报
温馨提示
。Arctic Studio是一个集成了gcc编译器的开发环境(powerpc-eabispe),同时包括了C语言编辑器CDT,在Professional版本中包含ECU的配置工具。
资源详情
资源评论
资源推荐
收起资源包目录
Arctic Core是AUTOSAR标准开放源码(GPL)的嵌入式系统平台 (2000个子文件)
studioide.clean.executable.win32.win32.x86_4.0.0 35KB
.mainData.2 1.15MB
.lazy.2 590KB
.extraData.2 330KB
.bundledata.2 96KB
.table.2 58KB
.state.2 34KB
.namespaces.2 10KB
.contributors.2 8KB
.contributions.2 7KB
.orphans.2 96B
org.eclipse.cdt_root_8.1.0.201206111645 8KB
.fileTable.6 95B
.fileTable.7 95B
.fileTable.8 160B
.fileTable.9 160B
ant 10KB
antRun 861B
.api_description 445B
.api_description 367B
.api_description 202B
bash_completion 11KB
ant.bat 7KB
antRun.bat 1KB
lcp.bat 1KB
splash.bmp 533KB
splash.bmp 159KB
splash.bmp 159KB
icon48.bmp 9KB
icon48.bmp 9KB
icon32.bmp 4KB
icon32.bmp 4KB
icon16.bmp 1KB
icon16.bmp 1KB
_0.cfs 235KB
_0.cfx 67KB
map-cmdline.changelog 842B
EclipseRSS1Viewer.class 10KB
SplashHandler.class 4KB
EclipseRSS1Viewer$RSSHandler.class 3KB
AutosarPerspective.class 2KB
SplashHandler$1.class 2KB
EclipseRSS1Viewer$NewsFeed$1.class 2KB
Activator.class 2KB
SplashHandler$2.class 1KB
EclipseRSS1Viewer$NewsFeed.class 1KB
Messages.class 1KB
EclipseRSS1Viewer$2.class 1KB
EclipseRSS1Viewer$1.class 1KB
EclipseRSS1Viewer$NewsItem.class 701B
.classpath 332B
envset.cmd 4KB
antenv.cmd 3KB
ant.cmd 3KB
runrc.cmd 2KB
map-cmdline.compact 460B
shared.css 14KB
shared.css 10KB
shared.css 10KB
root.css 9KB
root.css 8KB
style-monoblue.css 8KB
root.css 8KB
style.css 5KB
style-coal.css 5KB
style-paper.css 5KB
standby.css 4KB
standby.css 4KB
standby.css 4KB
shared.css 4KB
style-gitweb.css 4KB
narrow_book.css 3KB
book.css 3KB
book.css 3KB
rtl.css 3KB
style.css 2KB
font-relative.css 2KB
rtl.css 2KB
help.css 2KB
book.css 2KB
font-absolute.css 2KB
font-relative.css 2KB
rtl.css 2KB
font-absolute.css 2KB
font-relative.css 2KB
font-absolute.css 2KB
whatsnew.css 2KB
webresources.css 1KB
firststeps.css 1KB
tutorials.css 1KB
overview.css 1KB
samples.css 1KB
migrate.css 1KB
whatsnew.css 1KB
e4_default_winxp_blu.css 1KB
webresources.css 1KB
e4_default_mac.css 1KB
firststeps.css 1KB
e4_default_gtk.css 1KB
tutorials.css 1KB
共 2000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 20
bonson2004
- 粉丝: 201
- 资源: 11
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0