7
7
.. TODO: Should have some explanation of why you'd want things in
13
While most configuration is handled by configuration files, some options
14
which may be semi-permanent can also be controlled through the environment.
18
Override the email id used by Bazaar. Typical format::
20
"John Doe <jdoe@example.com>"
22
See also the ``email`` configuration value.
26
Override the progress display. Possible values are "none", "dots", "tty"
30
Control whether SIGQUIT behaves normally or invokes a breakin debugger.
31
0 = Standard SIGQUIT behavior
32
1 = Invoke breakin debugger (default)
36
Override the home directory used by Bazaar.
40
Select a different SSH implementation.
44
Control whether to launch a debugger on error.
50
Path to the Bazaar executable to use when using the bzr+ssh protocol.
52
See also the ``bzr_remote_path`` configuration value
56
Path to the editor Bazaar should use for commit messages, etc.
60
The path to the plugins directory that Bazaar should use.
64
The path where Bazaar should look for shell plugin external commands.
10
67
Location of configuration files
11
68
===============================
12
69
Each user gets a pair of configurations files in ``$HOME/.bazaar``. The first
253
These options apply only to branches that use the "experimental-branch6"
254
format. They are usually set in ``.bzr/branch/branch.conf`` automatically, but
255
may be manually set in ``locations.conf`` or ``bazaar.conf``.
310
These options apply only to branches that use the "dirstate-tags" format. They
311
are usually set in ``.bzr/branch/branch.conf`` automatically, but may be
312
manually set in ``locations.conf`` or ``bazaar.conf``.
257
314
append_revisions_only
258
315
---------------------
added
removed
doc/en/user-guide/configuration.txt
