all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: wael-zwaiter@gmx.com
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [External] : Cannot see what is written on modeline
Date: Tue, 18 May 2021 17:19:58 +0200	[thread overview]
Message-ID: <trinity-ea30b719-1a96-4eca-8a96-8308732008f9-1621351197973@3c-app-mailcom-bs13> (raw)
In-Reply-To: <874kf0yyrr.fsf@telefonica.net>






> Sent: Wednesday, May 19, 2021 at 1:09 AM
> From: "Óscar Fuentes" <ofv@wanadoo.es>
> To: help-gnu-emacs@gnu.org
> Subject: Re: [External] : Cannot see what is written on modeline
>
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: wael-zwaiter@gmx.com
> >> Cc: help-gnu-emacs@gnu.org
> >> Date: Tue, 18 May 2021 14:12:48 +0200
> >> 
> >> > Where did those colors come from? they are not the default colors.
> >> 
> >> I took them from calling
> >> 
> >>    M-x customize-face mode-line
> >
> > So you your self asked Emacs to use these colors? then I think Emacs
> > shouldn't second-guess you.
> 
> I think that the OP is saying that he looked up the colors through M-x
> customize-face, not that he *setted* them.
> 
> I asked him to make some experiments to determine the source of those
> colors, but his last message in our exchange contained only quoted text
> from previous messages.

I replied with the following

-q --no-x-resources Problem goes away

-q --no-site-file Problem exists

-q --no-site-lisp Problem exists

It was then determined that X Resource was doing that.
 
> > There could be a place to warn the user that these colors mean low
> > contrast, when the user is about to save the changes.  Would that be
> > good enough?
> 
> In general, that feature could avoid the scenario where by accident or
> ignorance the user sets a background and foreground so similar to each
> other that the customize-face interface itself becomes unreadable.

It isn't practical to set resources that are used by every application.
You'll need to add or override some settings for particular applications. 
 
> Instead of asking before applying the changes, is could be better to ask
> after the changes are visible, using a temporary "safe" color
> combination on the minibuffer: "your changes look like this, do you want
> to keep them?".
> 
> 
>



  reply	other threads:[~2021-05-18 15:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 18:16 Cannot see what is written on modeline wael-zwaiter
2021-05-17 22:47 ` [External] : " Drew Adams
2021-05-17 23:02   ` wael-zwaiter
2021-05-22  4:29     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-18  7:55   ` tomas
2021-05-18  8:02     ` wael-zwaiter
2021-05-18 11:59       ` Eli Zaretskii
2021-05-18 12:12         ` wael-zwaiter
2021-05-18 12:29           ` Eli Zaretskii
2021-05-18 13:01             ` wael-zwaiter
2021-05-18 13:17               ` Eli Zaretskii
2021-05-18 13:09             ` Óscar Fuentes
2021-05-18 15:19               ` wael-zwaiter [this message]
2021-05-18 14:03           ` Drew Adams
2021-05-18 14:33             ` wael-zwaiter
2021-05-18 14:45               ` Óscar Fuentes
2021-05-18 15:11                 ` tomas
2021-05-18 15:45                   ` Christopher Dimech
2021-05-17 23:38 ` Óscar Fuentes
2021-05-17 23:41   ` wael-zwaiter
2021-05-17 23:44     ` Óscar Fuentes
2021-05-17 23:49       ` wael-zwaiter
2021-05-18  0:12         ` Óscar Fuentes
2021-05-18  0:25           ` wael-zwaiter
2021-05-18  4:28             ` [External] : " Drew Adams
2021-05-18  7:55               ` RE: [External] : " wael-zwaiter
2021-05-18 13:09                 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-18 15:24                   ` Christopher Dimech
2021-05-19  7:53                     ` Robert Thorpe
2021-05-19  8:50                       ` michael-franzese
2021-05-18 13:13                 ` Óscar Fuentes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-ea30b719-1a96-4eca-8a96-8308732008f9-1621351197973@3c-app-mailcom-bs13 \
    --to=wael-zwaiter@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ofv@wanadoo.es \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.