summaryrefslogtreecommitdiff
path: root/lisp/proced.el
diff options
context:
space:
mode:
authorOlivier Certner <olce.emacs@certner.fr>2022-11-10 18:57:27 +0100
committerEli Zaretskii <eliz@gnu.org>2022-11-17 11:40:09 +0200
commitc8b9922e26a42db46411d1dea4e78089adf6743e (patch)
treefd6707ccbf81b9acd4507590d00e3376904d5b12 /lisp/proced.el
parenta0ee57c80dea105ab08aad3c0cdce11e43b5fa29 (diff)
downloademacs-c8b9922e26a42db46411d1dea4e78089adf6743e.tar.gz
emacs-c8b9922e26a42db46411d1dea4e78089adf6743e.tar.bz2
emacs-c8b9922e26a42db46411d1dea4e78089adf6743e.zip
ediff: Merges with ancestor: Fix computation of hunks and proposed merge
Hunks were not computed correctly because the diff3 command was invoked with arguments in an incorrect order. The correct order is the local file first, the base (or "ancestor") second and the other file third. This erroneous behavior had two consequences. First, the output of diff3 would change, since it tries to merge chunks according to maximal matches between the second and first files, and the second and third files. Second, ediff, more precisely, `ediff-do-merge', would consequently try to merge the reverse of the changes from the base to the other file. * lisp/vc/ediff-diff.el (ediff-setup-diff-regions3): In the arguments to `ediff-exec-process', swap the other file with the ancestor (only when merging with an ancestor). (ediff-extract-diffs3): Match the hunk data for the ancestor and the other file correctly. The local variable `three-way-comp' indicates this is a merge with ancestors when it is nil. (Bug#59182)
Diffstat (limited to 'lisp/proced.el')
0 files changed, 0 insertions, 0 deletions