From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58459@debbugs.gnu.org
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Wed, 12 Oct 2022 17:30:46 +0000 [thread overview]
Message-ID: <hEZXbSbK2JOn8pHSGcy1aEbffG0gnOh9jnQXX41_K7C0MVfGJBsM3ffTorkca2XDcgtvo0GuY-HD3ggLpXGFdElWLZOkjuqWn_v8JdkEybA=@proton.me> (raw)
In-Reply-To: <CADwFkmncATnVAOnLQmy9qZ8VxZT5MOZG7WtTSWSMewxeOVJsBQ@mail.gmail.com>
------- Original Message -------
On Wednesday, October 12th, 2022 at 4:23 PM, Stefan Kangas <stefankangas@gmail.com> wrote:
> uzibalqa uzibalqa@proton.me writes:
>
> > > Why is emacs not taking care of these EMACS generated X-Resources?
>
>
> I don't think Emacs would set these resources. My guess it's specific
> to your setup, or your GNU/Linux distribution or something.
>
> > > 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.
>
>
> It's a general feature on X that we happen to support. It's not a bug.
>
> > How can one unset those resources?
>
>
> If you read `man xrdb', you will find:
>
> xrdb -remove
Fine, let me agree it is not a bug. Because emacs supports some general features on X,
and we know that this problem might occur, could emacs also support the clearance of
EMACS X-Resources. Particularly for those not technically aware, it will solve them a
whole lot of problems.
next prev parent reply other threads:[~2022-10-12 17:30 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
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 [this message]
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='hEZXbSbK2JOn8pHSGcy1aEbffG0gnOh9jnQXX41_K7C0MVfGJBsM3ffTorkca2XDcgtvo0GuY-HD3ggLpXGFdElWLZOkjuqWn_v8JdkEybA=@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).