From: Stefan Kangas <stefankangas@gmail.com>
To: uzibalqa <uzibalqa@proton.me>, 58459@debbugs.gnu.org
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Wed, 12 Oct 2022 02:51:24 -0700 [thread overview]
Message-ID: <CADwFkmnizuZeg=i8HptBxNTORqrp456czbcRhvyWiNFvAkjyjg@mail.gmail.com> (raw)
In-Reply-To: <P7eKY8DiXYMVSHfTzVX2fRJjAsaFNXv--tUGF0pH9skDmzdFr9_peUTrkxjSrIJGrYNCiRiLU4uY9FwuDlta7q1hSGJyctqN78Dxwakk41A=@proton.me>
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.
next prev parent reply other threads:[~2022-10-12 9:51 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmnizuZeg=i8HptBxNTORqrp456czbcRhvyWiNFvAkjyjg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58459@debbugs.gnu.org \
--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 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.