From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: michael-franzese@gmx.com
Cc: Christopher Dimech <dimech@gmx.com>, help-gnu-emacs@gnu.org
Subject: Re: [External] : Cannot see what is written on modeline
Date: Wed, 19 May 2021 08:53:03 +0100 [thread overview]
Message-ID: <87v97fxiqo.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <trinity-198898e6-3a1e-4db2-b009-47fb6051be73-1621351479117@3c-app-mailcom-bs13> (message from Christopher Dimech on Tue, 18 May 2021 17:24:39 +0200)
I think there is some confusion about X resources here.
By default the X windowing system doesn't set any of the things that
we've been talking about. If you start with X and no special
configuration then Emacs uses the Emacs default settings.
X resources are something that someone sets. In this case you have set
an X resource for some reason that has interferred with Emacs'
functioning. The X windowing system itself has not created that
setting. Someone doing configuration has created that setting.
Maybe you copied an X resource snippet from the internet and that has
caused this.
At an outside chance it may be the distro that you are using that has
added this X resource. If so, that is a bug in the distro and should be
reported to the distro maintainers.
To check whether that is the cause you can create a new user account.
If "emacs" is run from that new account it should look like "emacs -Q".
If it does then a user-added X-resource is the problem. If the same
contrast problem occurs then the the distro probably has a bug.
This is the first time I've heard of a problem like this for Emacs. I
don't think it warrants a change to the way Emacs works.
BR,
Robert Thorpe
next prev parent reply other threads:[~2021-05-19 7:53 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
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 [this message]
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
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=87v97fxiqo.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael-franzese@gmx.com \
/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.
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).