From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: ajh@ajhurst.org, 73244@debbugs.gnu.org
Subject: bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41
Date: Sat, 21 Sep 2024 14:19:12 +0300 [thread overview]
Message-ID: <86y13l2r0v.fsf@gnu.org> (raw)
In-Reply-To: <8734lt1g7r.fsf@yahoo.com> (message from Po Lu on Sat, 21 Sep 2024 17:58:00 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: "John Hurst" <ajh@ajhurst.org>, 73244@debbugs.gnu.org
> Date: Sat, 21 Sep 2024 17:58:00 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Sat, 14 Sep 2024 12:42:50 +1000
> >> From: "John Hurst" <ajh@ajhurst.org>
> >>
> >> The bug I have, since upgrading to Ubuntu 24.04 and install emacs29 is that the initial frame has width x height of 20 x 9, even though I have a .Xresources file containing
> >> Emacs*geometry: 100x40+1900+0
> >> end a default-frame-alist of
> >> Value:
> >> ((font . "Monospace-10")
> >> (height . 42)
> >> (width . 90)
> >> (tool-bar-lines . 0)
> >> (menu-bar-lines . 1)
> >> (top . 0)
> >> (left . 1200))
> >> Original value was nil
> >> set up by my .emacs file.
> >>
> >> Using either the pull-down File->New Frame, or C-x 5 2, both generate new frames of the 20 x 9 size.
> >>
> >> I can send the .emacs file if needed, but note that "emacs -D' also gives the same default size of 20 x 9, so I don't think it is a problem with my .emacs file - which did work OK under Ubuntu 22.04 and emacs28.
> >
> > Po Lu, any comments or suggestions?
>
> >From what I've heard, the culprit is rather the upgrade to Ubuntu 24.04
> than to Emacs 29, and the problem will disappear if Emacs is configured
> with another toolkit than GTK.
Does it mean that GTK which comes with Ubuntu 24.04 is unusable with
Emacs? What exactly in GTK causes this?
next prev parent reply other threads:[~2024-09-21 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 2:42 bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41 John Hurst
2024-09-14 2:45 ` bug#73245: " John Hurst
2024-09-14 7:23 ` Eli Zaretskii
2024-09-14 7:25 ` bug#73244: " Eli Zaretskii
2024-09-21 9:50 ` Eli Zaretskii
2024-09-21 9:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-21 11:19 ` Eli Zaretskii [this message]
2024-10-05 9:55 ` Eli Zaretskii
2024-10-05 11:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 11:48 ` Eli Zaretskii
2024-10-13 21:29 ` John Hurst
2024-10-13 23:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 13:33 ` Eli Zaretskii
2024-10-14 15:58 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <1c429b02-0407-4f9c-8e94-f012463adb01@app.fastmail.com>
[not found] ` <fa8dff61-d923-4fcc-8e90-c76aeb355095@gmx.at>
[not found] ` <cb955552-3695-4160-9514-625b8426db33@app.fastmail.com>
2024-10-21 8:18 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <e8252eea-b499-4ce1-8e9d-6e7193ff8fb2@app.fastmail.com>
2024-10-21 8:19 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-22 23:59 ` John Hurst
2024-10-23 8:15 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 2:01 ` John Hurst
2024-10-26 8:43 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-27 7:32 ` John Hurst
2024-10-27 8:47 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <c1130417-c81a-43fc-b897-2df3633d0556@app.fastmail.com>
2024-11-16 8:59 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-16 11:05 ` John Hurst
2024-11-16 12:35 ` Eli Zaretskii
2024-11-16 16:39 ` martin rudalics 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=86y13l2r0v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73244@debbugs.gnu.org \
--cc=ajh@ajhurst.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 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.