17
17
If ``whoami`` is used without an argument, the current value is displayed.
22
If your network requires that you use an HTTP proxy for outbound
23
connections, you must set the ``http_proxy`` variable. If the proxy is
24
also required for https connections, you need to set ``https_proxy`` too.
25
If you need these and don't have them set, you may find that connections
26
to Launchpad or other external servers fail or time out.
28
On Unix you typically want to set these in ``/etc/environment`` or
29
``~/.bash_profile`` and on Windows in the user profile.
33
http_proxy=http://proxy.example.com:3128/
34
https_proxy=http://proxy.example.com:3128/
36
The ``no_proxy`` variable can be set to a comma-separated list of hosts
37
which shouldn't be reached by the proxy. (See
38
<http://docs.python.org/library/urllib.html> for more details.)
40
Various ways to configure
41
-------------------------
43
As shown in the example above, there are various ways to
44
configure Bazaar, they all share some common properties though.
47
- a name which is generally a valid python identifier,
49
- a value which is a string. In some cases, Bazaar will be able
50
to recognize special values like 'True', 'False' to infer a
51
boolean type, but basically, as a user, you will always specify
54
Options are grouped in various contexts so the option name
55
uniquely identifies it in this context. When needed, options can
56
be made persistent by recording them in a configuration file.
59
19
Configuration files
60
20
-------------------
62
Configuration files are located in ``$HOME/.bazaar`` on Unix and
22
Configuration files are located in ``$HOME/.bazaar`` on Linux/Unix and
63
23
``C:\Documents and Settings\<username>\Application Data\Bazaar\2.0`` on
64
24
Windows. There are three primary configuration files in this location:
84
44
email = Your Name <email@example.com>
86
46
For further details on the syntax and configuration settings supported, see
87
`Configuration Settings <../user-reference/index.html#configuration-settings>`_
47
`Configuration Settings <../user-reference/bzr_man.html#configuration-settings>`_
88
48
in the Bazaar User Reference.
91
Looking at the active configuration
92
-----------------------------------
94
To look at all the currently defined options, you can use the following
99
``bzr`` implements some rules to decide where to get the value of a
100
configuration option.
102
The current policy is to examine the existing configurations files in a
103
given order for matching definitions.
105
* ``locations.conf`` is searched first for a section whose name matches the
106
location considered (working tree, branch or remote branch),
108
* the current ``branch.conf`` is searched next,
110
* ``bazaar.conf`` is searched next,
112
* finally, some options can have default values generally defined in the
113
code itself and not displayed by ``bzr config`` (see `Configuration
114
Settings <../user-reference/index.html#configuration-settings>`_).
116
This is better understood by using ```bzr config`` with no arguments, which
117
will display some output of the form::
120
post_commit_to = commits@example.com
121
news_merge_files = NEWS
123
parent_location = bzr+ssh://bazaar.launchpad.net/+branch/bzr/
124
nickname = config-modify
125
push_location = bzr+ssh://bazaar.launchpad.net/~vila/bzr/config-modify/
129
Each configuration file is associated with a given scope whose name is
130
displayed before each set of defined options.
132
Modifying the active configuration
133
----------------------------------
135
To set an option to a given value use::
139
To remove an option use::
141
bzr config --remove opt
144
51
Rule-based preferences
145
52
----------------------
149
56
``BZR_HOME/rules``.
151
58
For further information on how rules are searched and the detailed syntax of
152
the relevant files, see `Rules <../user-reference/index.html#rules>`_
59
the relevant files, see `Rules <../user-reference/bzr_man.html#rules>`_
153
60
in the Bazaar User Reference.
156
Escaping command lines
157
----------------------
159
When you give a program name or command line in configuration, you can quote
160
to include special characters or whitespace. The same rules are used across
163
The rules are: strings surrounded by double-quotes are interpreted as single
164
"words" even if they contain whitespace, and backslash may be used to quote
165
quotation marks. For example::
167
BZR_EDITOR="C:\Program Files\My Editor\myeditor.exe"
added
removed
doc/en/user-guide/configuring_bazaar.txt
