From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: 58459@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Wed, 12 Oct 2022 12:56:37 +0000 [thread overview]
Message-ID: <TNOxUn5VEuFWnIJWisQ_IJWqPL4o2s2WygM0ZL4z2Nm0v8oEWTblxobGDcnmDZTa9YWR5dsqdaSWl01jx9zR3RGCLv6fQFkmfPnyGitz7l0=@proton.me> (raw)
In-Reply-To: <1M2WN8RSJh3rnvRYoGKu2FOYFosKFsYxRLesaZKzA6dmdXLvGsxZNON-D3zRMgv-FkPqF2qFTurWu3u2ruoKK1QSzHheoICPo2MIi7VR6lc=@proton.me>
------- Original Message -------
On Wednesday, October 12th, 2022 at 12:52 PM, uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> ------- Original Message -------
> On Wednesday, October 12th, 2022 at 9:51 AM, Stefan Kangas stefankangas@gmail.com wrote:
>
>
>
> > tags 58459 notabug
> > close 58459
> > thanks
> >
> > uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text
> > editors" bug-gnu-emacs@gnu.org writes:
> >
> > > I am finding it extremely difficult to get a fresh emacs configuration. Even after removing
> > > my "~/.emacs" file and even with "emacs -q" which should not load any init file, I get a black
> > > background when I do "emacs -q". With customize-themes not showing that any theme is selected.
> > >
> > > Even the command
> > >
> > > emacs -q --no-site-file --no-splash
> > >
> > > gives me a black background.
> > >
> > > But "emacs -Q" gives me a white background.
> >
> > So you have some X resources that are causing you trouble. See the
> > documentation for the -Q flag.
> >
> > Try this to see:
> >
> > xrdb -query -all|grep -i emacs
> >
> > And then unset those resources.
> >
> > This is a support question and not a bug, so I'm closing this.
>
>
> Why is emacs not taking care of these EMACS generated X-Resources?
> You may claim it is not a bug, but what would be the usefelness when
> user wants a fresh restart but has to go through all this torture
> to find out what is going on. It is definitely not for the novice
> to fix this.
How can one unset those resources?
--------------------------------------
This is the result of xrdb
xrdb -query -all | grep -i emacs
Emacs*Background: #000000
Emacs*Dialog*background: #000000
Emacs*Dialog*foreground: #ffffff
Emacs*Foreground: #ffffff
Emacs*XlwScrollBar.Background: #000000
Emacs*XlwScrollBar.Foreground: #ffffff
Emacs*backgroundToolBarColor: #000000
Emacs*bottomToolBarShadowColor: #000000
Emacs*menubar*background: #000000
Emacs*menubar*foreground: #ffffff
Emacs*popup*Background: #000000
Emacs*popup*Foreground: #ffffff
Emacs*topToolBarShadowColor: #000000
Emacs.default.attributeBackground: #000000
Emacs.default.attributeForeground: #ffffff
Emacs.mode-line.attributeForeground: #ffffff
Emacs.scroll-bar.attributeBackground: #000000
Emacs.scroll-bar.attributeForeground: #ffffff
Emacs.tool-bar.attributeBackground: #000000
Emacs.tool-bar.attributeForeground: #ffffff
next prev parent reply other threads:[~2022-10-12 12:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 0:09 bug#58459: Getting a fresh emacs session with no customisation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 9:51 ` Stefan Kangas
2022-10-12 12:52 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 12:56 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-12 16:23 ` Stefan Kangas
2022-10-12 17:30 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 21:11 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 22:47 ` Phil Sainty
2022-10-12 23:16 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 1:14 ` Stefan Kangas
2022-10-13 2:02 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 3:01 ` Stefan Kangas
2022-10-13 15:48 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 10:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:09 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:52 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:27 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:36 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:56 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 15:47 ` Eli Zaretskii
2022-10-13 16:06 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 16:20 ` Eli Zaretskii
2022-10-13 17:51 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 18:35 ` Christopher Dimech
2022-10-14 8:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 19:40 ` Christopher Dimech
2022-10-13 16:36 ` Christopher Dimech
2022-10-13 19:13 ` Eli Zaretskii
2022-10-13 19:20 ` Christopher Dimech
2022-10-13 10:30 ` Po Lu 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='TNOxUn5VEuFWnIJWisQ_IJWqPL4o2s2WygM0ZL4z2Nm0v8oEWTblxobGDcnmDZTa9YWR5dsqdaSWl01jx9zR3RGCLv6fQFkmfPnyGitz7l0=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=58459@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--cc=uzibalqa@proton.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).