unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: contovob@tcd.ie, 46493@debbugs.gnu.org,
	Yuuki Harano <masm+emacs@masm11.me>
Subject: bug#46493: [feature/pgtk] Low contrast region face
Date: Mon, 20 Jun 2022 00:41:45 +0200	[thread overview]
Message-ID: <878rpstgwm.fsf@gnus.org> (raw)
In-Reply-To: <878rpszuig.fsf@yahoo.com> (Po Lu's message of "Sun, 19 Jun 2022 20:51:19 +0800")

Po Lu <luangruo@yahoo.com> writes:

>> However, we ignore the theme for everything else, so "emacs -Q" gives me
>> an Emacs with a white background -- and a very dark region face.
>
> That shouldn't be problematic, right? Because we have the distant
> foreground set to the GTK region foreground color, so there will always
> be sufficient contrast.

It's nonsensical of Emacs to use the Gtk theme for just one colour here.
It should either use the Gtk theme for the background/foreground
colours, too, or not use it at all.

> Users using a non-default GTK stylesheet should know of the
> consequences, and can simply customize the region face to use a
> different background color.

Emacs composes the colours we use here, and we choose colours that have
the mixture we want.  Our current approach leads to two bugs: With a
dark theme, we get a nonsensically dramatic region face, and with a
light theme, we get a region face that has too low contrast.  That's an
Emacs bug, and not something the user should have to deal with.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-19 22:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 16:55 bug#46493: [feature/pgtk] Low contrast region face Basil L. Contovounesios
2021-02-13 20:21 ` Dmitry Gutov
2021-02-13 20:53   ` Basil L. Contovounesios
2021-02-13 21:12     ` Dmitry Gutov
2021-02-14 12:48       ` Basil L. Contovounesios
2021-02-14  3:59 ` Yuuki Harano
2021-02-14 13:00   ` Basil L. Contovounesios
2021-02-15 17:06     ` Yuuki Harano
2021-02-15 19:20       ` Basil L. Contovounesios
2022-06-17 13:41   ` Lars Ingebrigtsen
2022-06-18  1:58     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-18 10:04       ` Lars Ingebrigtsen
2022-06-19  2:36         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-19 11:11           ` Lars Ingebrigtsen
2022-06-19 11:54             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-19 12:02               ` Lars Ingebrigtsen
2022-06-19 12:51                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-19 22:41                   ` Lars Ingebrigtsen [this message]
2022-06-20  0:59                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20  1:12                       ` Lars Ingebrigtsen
2022-06-20  1:44                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23  8:53                         ` Lars Ingebrigtsen
2022-07-23  8:59                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23  9:09                             ` Lars Ingebrigtsen
2022-07-23  9:18                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23  9:37                                 ` Lars Ingebrigtsen
2022-06-18 15:43       ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=878rpstgwm.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46493@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=luangruo@yahoo.com \
    --cc=masm+emacs@masm11.me \
    /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).