From: Michael Heerdegen via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: BUG: ediff-buffers does not consistently show "differences" or "difference regions" within the "active region"
Date: Sat, 20 Jul 2024 09:04:19 +0200 [thread overview]
Message-ID: <874j8kh7d8.fsf@web.de> (raw)
In-Reply-To: h6zlkxvqSlYlEu2zIKRfTxeXnP3lIJo5q15igV0IPDmF_Tb08czVMYW3sorJijKUN9K2jslCKtl-3t5H40gMJL42suaYDgA5csa6NG98k5M=@protonmail.com
gnuist <gnuist@protonmail.com> writes:
> You will immediately see that TAB is not highlighed in file A in its
> first line. This is *inconsistent* because in the second case c#d the
> hash is highlighted as the difference region within active region.
Just to be clear: You are talking about fine diff highlighting?
I think whitespace is ommitted when highlighting fine diffs to make the
result appear less distracting in the majority of cases.
When the corresponding change counterpart in the other buffer is not
(only) whitespace it may be wishful to highlight the whitespace in the
other diff buffer, depending on the case.
> Anyone at FSF/gnu to explain what appears to be such a basic bug
> staying there for so long?
Not speaking officially for them: We are just all too dumb I guess.
Michael.
prev parent reply other threads:[~2024-07-20 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 19:53 BUG: ediff-buffers does not consistently show "differences" or "difference regions" within the "active region" gnuist
2024-07-20 7:04 ` Michael Heerdegen via Users list for the GNU Emacs text editor [this message]
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=874j8kh7d8.fsf@web.de \
--to=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).