From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: 33567@debbugs.gnu.org
Subject: bug#33567: Syntactic fontification of diff hunks
Date: Wed, 26 Dec 2018 03:40:46 +0200 [thread overview]
Message-ID: <b55cbf8a-2be9-f6b3-bbd5-2f85e89675a6@yandex.ru> (raw)
In-Reply-To: <87lg4ds5zi.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On 25.12.2018 22:39, Juri Linkov wrote:
>> Your proposed new colors for added/removed are the same that are used
>> GitHub/GitLab, so this should be a good change. For refine-removed
>> better to use GitLab's color #ffcccc that is very close to the
>> color you proposed. But for refine-added GitLab made the same mistake
>> that GitHub already fixed. So the best color for refine-added is #bbffbb.
>
> After trying to use there colors, I see that their shade is too subtle.
> They might look better on large hunks, and I'm not sure why they look ok
> in the browser, but in Emacs refined colors for small changes are almost
> not noticeable. However, please change them if majority agrees.
To my eyes, that's a surprising conclusion.
I wasn't going to argue with your correction to refine-added, even
though I might prefer a slightly lighter variation (because I end up
looking at larger refined regions often). Are you now saying that
#ffcccc for refine-removed (or #d0ffd0, the difference is visible only
on large regions) and #bbffbb for refine-added are hard for you to
notice on smaller regions?
It most likely depends on the choice of the font, the contrast levels of
the monitor and similar stuff, but during the same several days I have
not met the same experience.
Before we get into deeper discussion (as well as discussing how one
finds out majority's opinion), I have to ask: did you make sure to use
the new refined colors with the new diff-added and diff-removed
background colors?
Attached are the screenshots of the default theme with my preferred font
(Inconsolata LGC) and refined colors from your counter-proposal. The
default Ubuntu's monospaced font is even more prominent and arguably
readable, I can make screenshots with it as well if you like.
This is commit a94ac604d8. We can also note that GitHub only refines
smaller chunks:
https://github.com/emacs-mirror/emacs/commit/a94ac604d8c9848b0414ade80a1920b345161656,
so its use of darker backgrounds is more justifiable.
What do you think of the screenshots? Are the small refined regions hard
for you to see? Or do they look very different in your Emacs?
[-- Attachment #2: Screenshot from 2018-12-26 03-28-06.png --]
[-- Type: image/png, Size: 432848 bytes --]
[-- Attachment #3: Screenshot from 2018-12-26 03-28-44.png --]
[-- Type: image/png, Size: 364018 bytes --]
[-- Attachment #4: Screenshot from 2018-12-26 03-29-20.png --]
[-- Type: image/png, Size: 363806 bytes --]
next prev parent reply other threads:[~2018-12-26 1:40 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 21:55 bug#33567: Syntactic fontification of diff hunks Juri Linkov
2018-12-02 6:56 ` Eli Zaretskii
2018-12-03 0:34 ` Juri Linkov
2018-12-03 6:49 ` Eli Zaretskii
2018-12-03 23:36 ` Juri Linkov
2018-12-04 7:01 ` Eli Zaretskii
2018-12-04 23:16 ` Juri Linkov
2018-12-05 7:19 ` Eli Zaretskii
2018-12-05 23:25 ` Juri Linkov
2018-12-06 6:53 ` Eli Zaretskii
2018-12-11 0:38 ` Juri Linkov
2018-12-11 6:23 ` Eli Zaretskii
2018-12-12 0:28 ` Juri Linkov
2018-12-12 17:11 ` Eli Zaretskii
2018-12-03 23:59 ` Juri Linkov
2018-12-04 7:36 ` Eli Zaretskii
2018-12-04 23:28 ` Juri Linkov
2018-12-05 7:25 ` Eli Zaretskii
2018-12-05 23:35 ` Juri Linkov
2018-12-12 23:17 ` Juri Linkov
2018-12-14 9:13 ` Eli Zaretskii
2018-12-16 23:27 ` Juri Linkov
2018-12-17 16:13 ` Eli Zaretskii
2018-12-17 23:11 ` Juri Linkov
2018-12-18 0:14 ` Juri Linkov
2018-12-18 15:55 ` Dmitry Gutov
2018-12-18 22:35 ` Juri Linkov
2018-12-18 23:33 ` Dmitry Gutov
2018-12-19 0:11 ` Juri Linkov
2018-12-19 0:48 ` Dmitry Gutov
2018-12-19 1:35 ` Dmitry Gutov
2018-12-19 21:49 ` Juri Linkov
2018-12-19 22:50 ` Dmitry Gutov
2018-12-20 22:00 ` Juri Linkov
2018-12-24 2:29 ` Dmitry Gutov
2018-12-25 20:35 ` Juri Linkov
2018-12-25 21:15 ` Dmitry Gutov
2018-12-26 22:49 ` Juri Linkov
2018-12-26 23:16 ` Dmitry Gutov
2018-12-27 0:18 ` Juri Linkov
2018-12-27 0:45 ` Dmitry Gutov
2018-12-27 3:34 ` Eli Zaretskii
2018-12-27 3:32 ` Eli Zaretskii
2018-12-19 21:51 ` Juri Linkov
2018-12-20 0:11 ` Dmitry Gutov
2018-12-20 21:50 ` Juri Linkov
2018-12-20 1:15 ` Dmitry Gutov
2018-12-20 22:17 ` Juri Linkov
2018-12-25 20:39 ` Juri Linkov
2018-12-26 1:40 ` Dmitry Gutov [this message]
2018-12-26 22:59 ` Juri Linkov
2018-12-26 23:56 ` Dmitry Gutov
2018-12-27 20:39 ` Juri Linkov
2018-12-29 23:07 ` Juri Linkov
2018-12-30 23:07 ` Dmitry Gutov
2018-12-26 0:43 ` Dmitry Gutov
2018-12-03 11:24 ` Dmitry Gutov
2018-12-03 23:24 ` Juri Linkov
2018-12-04 0:20 ` Dmitry Gutov
2018-12-04 6:46 ` Eli Zaretskii
2018-12-04 22:58 ` Juri Linkov
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=b55cbf8a-2be9-f6b3-bbd5-2f85e89675a6@yandex.ru \
--to=dgutov@yandex.ru \
--cc=33567@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).