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

Eli Zaretskii wrote:

> 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.

Ah, thanks, I hadn't realized that there were hidden annotations.  I
thought all the magic incantations were in the local variable settings
at the end of the buffer.

Are the charset tags (annotations) really necessary, given the setting
of 'coding' in the local variables?  (If the answer is "yes" and there
is documentation available that would explain why, feel free to simply
point me at the documentation.  If the answer is "yes" and there's no
documentation, feel free to just say "yes".  I understand that this area
of Emacs can be complicated, and I don't really need to know the
details.)  

The reason I ask is that the files that I saved last night from the old
and new Ediff buffers can be reloaded, and Ediff is able to correctly
show the changes.  Yet I don't see any visual distinctions between the
new file and etc/HELLO, even though the new file's mode is just
Fundamental, not Fundamental Enriched.  (Even the orange text on lines 1
and 34 is duplicated in the saved file, which I confess puzzles me.)

mike





  reply	other threads:[~2022-11-07 15:49 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
2022-11-07 15:49   ` Mike Kupfer [this message]
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=5768.1667836176@alto \
    --to=mkupfer@alum.berkeley.edu \
    --cc=59094@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).