Re: RE: [External] : Cannot see what is written on modeline

[wael-zwaiter@gmx.com]

> Sent: Wednesday, May 19, 2021 at 2:03 AM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "wael-zwaiter@gmx.com" <wael-zwaiter@gmx.com>, "Eli Zaretskii" <eliz@gnu.org>
> Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> Subject: RE: [External] : Cannot see what is written on modeline
>
> > > > Currently the colours are
> > > >
> > > > foreground: #ffffff
> > > > Background: #bfbfbf (grey75)
> > > >
> > > > The contrast ratio for such combination is 1.8,
> > > >
> > > > This level does not even reach the minimum contrast of 3.0 for
> > large scale text.
> > > >
> > > > Emacs should start caring about colour contrast by itself.
> > >
> > > Where did those colors come from? they are not the default colors.
> >
> > I took them from calling
> >
> >    M-x customize-face mode-line
>
> Then you (or something you loaded) customized that face.
>
> The point in telling you about `M-x customize-face' was
> that you can use that to revert to the uncustomized
> (default) appearance, and you can use it to customize
> faces to any appearance you like.

Should emacs allow X-Resource customisations when the result is not good
because it does not take into account computations based on the contrast
ratio?

I am of the view that emacs should by default set such things as the mode-line
itself and not allow X-Environment to take over.