unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Po Lu <luangruo@yahoo.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, 58489@debbugs.gnu.org
Subject: bug#58489: 29.0.50; commit 74c07733698b95eb455edcafab8634a700a3194f breaks GTK version for some Ubuntu distributions
Date: Fri, 14 Oct 2022 08:45:07 +0200	[thread overview]
Message-ID: <878rlioqdo.fsf@mat.ucm.es> (raw)
In-Reply-To: <87edvcyo8i.fsf@mat.ucm.es>


[-- Attachment #1.1: Type: text/plain, Size: 356 bytes --]

>>> "PL" == Po Lu <luangruo@yahoo.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>> So do you want be to have early-init.el in my home directory or in emacs/src?

> In your home directory.

>> How should I start emacs then?

> Without "emacs -Q", if the bug can be reproduced that way.

Ok, interesting:
first the screenshots of emacs -Q and emacs -q

[-- Attachment #1.2: emacs-emacs-q.png --]
[-- Type: image/png, Size: 332376 bytes --]

[-- Attachment #1.3: emacs-emacs-Q.png --]
[-- Type: image/png, Size: 256579 bytes --]

[-- Attachment #1.4: Type: text/plain, Size: 135 bytes --]


Then the screenshot with the early-init

It seems to look ok but when it finishes loading all my init files, it
looks like emacs -Q



[-- Attachment #1.5: emacs-emacs-full.png --]
[-- Type: image/png, Size: 343175 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2022-10-14  6:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 11:09 bug#58489: 29.0.50; commit 74c07733698b95eb455edcafab8634a700a3194f breaks GTK version for some Ubuntu distributions Uwe Brauer
2022-10-14  2:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  5:34   ` Uwe Brauer
2022-10-14  6:15     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  6:45       ` Uwe Brauer [this message]
2022-10-14  7:05         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  7:23           ` Uwe Brauer
2022-10-14  7:36             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  7:44               ` Uwe Brauer
2022-10-14  7:54                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  7:58                   ` Uwe Brauer
2022-10-14  8:01                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14  7:27           ` Uwe Brauer
2022-10-14  7:36             ` 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=878rlioqdo.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=58489@debbugs.gnu.org \
    --cc=luangruo@yahoo.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.
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).