unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: 59094@debbugs.gnu.org
Subject: bug#59094: 29.0.50; ediff-revision flags wrong lines in etc/HELLO
Date: Mon, 07 Nov 2022 17:10:36 +0200	[thread overview]
Message-ID: <835yfqztoz.fsf@gnu.org> (raw)
In-Reply-To: <60611.1667798946@alto> (message from Mike Kupfer on Sun, 06 Nov 2022 21:29:06 -0800)

> From: Mike Kupfer <mkupfer@alum.berkeley.edu>
> Date: Sun, 06 Nov 2022 21:29:06 -0800
> 
> From the top level directory of the git repository, running "emacs -Q":
> 
> 1. C-c C-f etc/HELLO RET
> 
> 2. M-x ediff-revision RET HELLO RET 0df73dabc16 RET 8721e87a6ec RET
> 
> Ediff says there are 6 diffs.  When I move through the diffs (e.g., by
> typing SPC in the Ediff control buffer), the first 4 claim that a line
> has been added, but that line already exists in the old revision (see
> attached screenshot).  These are the lines for Batak, Efik, Hanifi
> Rohingya, and Rejang.
> 
> Furthermore, ediff does not flag lines that actually are new: Adlam,
> Coptic, Gothic, Mende Kikakui, and Wancho.  Nor does it catch the change
> to Ukrainian.

I don't think Ediff can cope with portions of the file that disappear
from buffer text.  All the annotations that enriched.el eats up when
decoding the file are visible to Diff, and they get in the way of
counting characters.

Note that the real diffs also have 6 changes, just not where Ediff
shows them.





  reply	other threads:[~2022-11-07 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  5:29 bug#59094: 29.0.50; ediff-revision flags wrong lines in etc/HELLO Mike Kupfer
2022-11-07 15:10 ` Eli Zaretskii [this message]
2022-11-07 15:49   ` Mike Kupfer
2022-11-07 16:49     ` Eli Zaretskii
2022-11-07 20:26       ` Mike Kupfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835yfqztoz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59094@debbugs.gnu.org \
    --cc=mkupfer@alum.berkeley.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).