From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: 26969@debbugs.gnu.org
Cc: Justin Burkett <justin@burkett.cc>
Subject: bug#26969: 26.0.50; diff-changed invisible by default
Date: Wed, 17 May 2017 15:12:50 -0400 [thread overview]
Message-ID: <jwvmvabmh59.fsf@ceviche> (raw)
Package: Emacs
Version: 26.0.50
Nowadays the `diff-changed` face is defined to be "invisible" (i.e. the
text is displayed identically with or without that face).
IOW it can only be used as a parent of diff-added or diff-removed (or
some other such face).
This is a bad idea since in cases such as vdiff.el where some changes
are neither additions nor removals, it would make sense to highlight the
buffer as just "changed" and using that face is a natural choice.
I suggest the patch below for that. It is designed such that it should
make no visible difference to users of diff-added and diff-removed since
these faces override the parts that are set by my patch in diff-changed.
Another option would be to introduce a new face (not sure how to call
it, maybe diff-unspecified-change, maybe?) which inherits from
diff-changed as well.
Stefan
diff --git a/lisp/vc/diff-mode.el b/lisp/vc/diff-mode.el
index aa8d77882e..1aa6c05662 100644
--- a/lisp/vc/diff-mode.el
+++ b/lisp/vc/diff-mode.el
@@ -290,9 +290,14 @@ diff-added
:group 'diff-mode)
(defface diff-changed
- '((t nil))
+ '((((class color) (min-colors 88) (background light))
+ :background "grey90")
+ (((class color) (min-colors 88) (background dark))
+ :background "grey20")
+ (((class color))
+ :foreground "grey"))
"`diff-mode' face used to highlight changed lines."
- :version "25.1"
+ :version "26.1"
:group 'diff-mode)
(defface diff-indicator-removed
next reply other threads:[~2017-05-17 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 19:12 Stefan Monnier [this message]
2017-05-22 20:19 ` bug#26969: 26.0.50; diff-changed invisible by default Juri Linkov
2017-05-22 22:10 ` Stefan Monnier
2020-08-24 15:10 ` Lars Ingebrigtsen
2021-08-13 13:37 ` Lars Ingebrigtsen
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=jwvmvabmh59.fsf@ceviche \
--to=monnier@iro.umontreal.ca \
--cc=26969@debbugs.gnu.org \
--cc=justin@burkett.cc \
/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).