comparison tests/test-merge-tools.t @ 39124:6618634e3325

filemerge: show warning if chosen tool has no binary files capability

While matching patterns in "merge-patterns" configuration, Mercurial
silently assumes that all merge tools have binary files
capability. This implementation comes from 5af5f0f9d724 (or Mercurial
1.0).

At failure of merging binary files with incorrect internal merge tool,
there is no hint about this silent ignorance of binary files
capability.

This patch shows warning message, if chosen internal merge tool has no
binary files capability. This will help users to investigate why a
binary file isn't merged as expected.

39123:4d7b11877dd0

  merging f and f.txt to f.txt
  $TESTTMP/hgmerge.*/f~base $TESTTMP/hgmerge.*/f~local.txt $TESTTMP/hgmerge.*/f~other.txt $TESTTMP/repo/f.txt (glob)
  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)

Check that debugpicktool examines which merge tool is chosen for
specified file as expected

  $ beforemerge
  [merge-tools]

  $ hg debugpickmergetool --changedelete
  f = :prompt

(-r REV causes checking files in specified revision)

  $ hg manifest -r tip
  f.txt
  $ hg debugpickmergetool -r tip
  f.txt = true

#if symlink

(symlink causes chosing :prompt)

39124:6618634e3325

  merging f and f.txt to f.txt
  $TESTTMP/hgmerge.*/f~base $TESTTMP/hgmerge.*/f~local.txt $TESTTMP/hgmerge.*/f~other.txt $TESTTMP/repo/f.txt (glob)
  0 files updated, 1 files merged, 0 files removed, 0 files unresolved
  (branch merge, don't forget to commit)

Binary files capability checking

  $ hg update -q -C 0
  $ python <<EOF
  > with open('b', 'wb') as fp:
  >     fp.write(b'\x00\x01\x02\x03')
  > EOF
  $ hg add b
  $ hg commit -qm "add binary file (#1)"

  $ hg update -q -C 0
  $ python <<EOF
  > with open('b', 'wb') as fp:
  >     fp.write(b'\x03\x02\x01\x00')
  > EOF
  $ hg add b
  $ hg commit -qm "add binary file (#2)"

By default, binary files capability of internal merge tools is not
checked strictly.

(for merge-patterns, chosen unintentionally)

  $ hg merge 9 \
  > --config merge-patterns.b=:merge-other \
  > --config merge-patterns.re:[a-z]=:other
  warning: check merge-patterns configurations, if ':merge-other' for binary file 'b' is unintentional
  (see 'hg help merge-tools' for binary files capability)
  merging b
  warning: b looks like a binary file.
  0 files updated, 0 files merged, 0 files removed, 1 files unresolved
  use 'hg resolve' to retry unresolved file merges or 'hg merge --abort' to abandon
  [1]
  $ hg merge --abort -q

Check that debugpicktool examines which merge tool is chosen for
specified file as expected

  $ beforemerge
  [merge-tools]

  $ hg debugpickmergetool --changedelete
  f = :prompt

(-r REV causes checking files in specified revision)

  $ hg manifest -r 8
  f.txt
  $ hg debugpickmergetool -r 8
  f.txt = true

#if symlink

(symlink causes chosing :prompt)