From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 16514@debbugs.gnu.org
Subject: bug#16514: 24.3.50; Region overlay looks bad on refined hunks in diff-mode
Date: Sun, 06 Dec 2020 15:55:01 +0100 [thread overview]
Message-ID: <87lfebassa.fsf@gnus.org> (raw)
In-Reply-To: <87y52arljh.fsf@yandex.ru> (Dmitry Gutov's message of "Tue, 21 Jan 2014 06:44:34 +0200")
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Dmitry Gutov <dgutov@yandex.ru> writes:
> 1. Make some changes, save, open vc-diff buffer.
>
> 2. Extend region over the pieces of the hunk that `diff-refine-hunk'
> highlighted.
>
> If there are only a few such pieces, you only see a discrepancy between
> the pieces where region starts and ends (if either is within a refined
> part), because the region is partly visible there.
>
> If most of the hunk was refined (a lot of changes), however, the region
> becomes mostly invisible (aside from the bits between reginements).
I'm not sure I understand the recipe at all, but what I did was
C-x v =
in a file that had changes, and then created a region with the mouse
over an arbitrary bit of that buffer:
[-- Attachment #2: Type: image/png, Size: 88951 bytes --]
[-- Attachment #3: Type: text/plain, Size: 236 bytes --]
And the results don't look obviously wrong to me. So is this something
that has been fixed already, or am I reproducing it wrong?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-06 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 4:44 bug#16514: 24.3.50; Region overlay looks bad on refined hunks in diff-mode Dmitry Gutov
2020-12-06 14:55 ` Lars Ingebrigtsen [this message]
2020-12-06 15:39 ` Kévin Le Gouguec
2020-12-06 15:48 ` Kévin Le Gouguec
2020-12-06 15:58 ` Eli Zaretskii
2020-12-06 19:34 ` Dmitry Gutov
2020-12-06 19:56 ` Eli Zaretskii
2020-12-06 16:10 ` Andreas Schwab
2020-12-07 13:19 ` Lars Ingebrigtsen
2020-12-06 19:33 ` Dmitry Gutov
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=87lfebassa.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16514@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).