Bazaar

Merge lp:~vila/bzr/mergetool-doc into lp:bzr

  1. mergetool-doc
  2. Merge into bzr.dev
Proposed by Vincent Ladeuil
Status: Merged
Approved by: Martin Packman
Approved revision: no longer in the source branch.
Merged at revision: 6569
Proposed branch: lp:~vila/bzr/mergetool-doc
Merge into: lp:bzr
Diff against target: 25 lines (+16/-0)
1 file modified
bzrlib/help_topics/en/configuration.txt (+16/-0)
To merge this branch: bzr merge lp:~vila/bzr/mergetool-doc
Reviewer Review Type Date Requested Status
Martin Packman (community) Approve
Review via email: mp+125150@code.launchpad.net

Commit message

Clarify how `mergetool` templates should be used with `bzr config`.

Description of the change

Basde on an IRC discussion with mgz.

I think that should address
https://answers.launchpad.net/bzr/+question/196441 confusion.

To post a comment you must log in.
Revision history for this message
Martin Packman (gz) wrote :

So, I don't like "the following will (rightly) break", and perhaps we don't want to give the "wrong" version at all, but perhaps it's useful for people doing a search on the error message? So, just tone down the "we write software that's hard to use on purpose" angle and this should be fine.

review: Approve
Revision history for this message
Vincent Ladeuil (vila) wrote :

Is that better ?

Revision history for this message
Martin Packman (gz) wrote :

Typo, 'conflit'. But actually I find the sentence still rather hard to read, let's see if I can help...

"""
Because mergetool and config itself both use curly braces as interpolation markers, trying to display the mergetool line results in the following problem:

...

To avoid this, config can be instructed not to try expanding variables:

...
"""

Something like that? This is user-focused after all, so they shouldn't really care too much about the details.

Revision history for this message
Vincent Ladeuil (vila) wrote :

> Typo, 'conflit'. But actually I find the sentence still rather hard to read,
> let's see if I can help...

Thanks ;)

> Something like that? This is user-focused after all, so they shouldn't really
> care too much about the details.

Agreed, done.

Revision history for this message
Vincent Ladeuil (vila) wrote :

sent to pqm by email

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'bzrlib/help_topics/en/configuration.txt'
2--- bzrlib/help_topics/en/configuration.txt 2012-06-20 13:58:18 +0000
3+++ bzrlib/help_topics/en/configuration.txt 2012-10-10 18:32:18 +0000
4@@ -713,6 +713,22 @@
5
6 bzr.mergetool.kdiff3 = kdiff3 {base} {this} {other} -o {result}
7
8+Because ``mergetool`` and ``config`` itself both use curly braces as
9+interpolation markers, trying to display the mergetool line results in the
10+following problem::
11+
12+
13+ $ bzr config bzr.mergetool.kdiff3='kdiff3 {base} {this} {other} -o {result}'
14+ $ bzr config bzr.mergetool.kdiff3
15+ bzr: ERROR: Option base is not defined while expanding "kdiff3 {base} {this} {other} -o {result}".
16+
17+To avoid this, ``config`` can be instructed not to try expanding variables::
18+
19+ $ bzr config --all bzr.mergetool.kdiff3
20+ branch:
21+ bzr.mergetool.kdiff3 = kdiff3 {base} {this} {other} -o {result}
22+
23+
24 bzr.default_mergetool
25 ~~~~~~~~~~~~~~~~~~~~~
26