From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: John Hurst <ajh@ajhurst.org>
Cc: 73244@debbugs.gnu.org
Subject: bug#73244: Emacs29.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41
Date: Sun, 27 Oct 2024 09:47:41 +0100 [thread overview]
Message-ID: <306d175c-6134-4797-a4a6-9b1ab477f62c@gmx.at> (raw)
In-Reply-To: <4119539d-3042-4602-85bb-5d6aeb40c7cf@app.fastmail.com>
> I have to admit that I am getting out of my depth here. I have
> written lots of emacs lisp programs, but not using many of the
> features that you talk about. Hence I may get confused at times (:-(
In the area of Emacs/WM interactions I'm confused all the time.
>> This history is remarkable because I nowhere see that small frame size
>> in the ConfigureNotify events you got. Hence, you should not have seen
>> any strange resizings and no GTK warnings either. Am I right?
>
> Unfortunately, no. Still same small window, and 4 GTK warnings
This would mean that the frame size history would lie. Please repeat
the experiment:
(1) The early-init.el file has to contain
(setq frame-size-history '(100))
(defun resize-me (frame)
(set-frame-size frame 90 42))
(add-hook 'after-make-frame-functions 'resize-me)
and there should be no .emacs file, no resources for Emacs.
(2) Run emacs from the launch bar.
(3) Maximize the emacs frame and evaluate (frame--size-history).
(4) Post the contents of the *frame-size-history* buffer here.
>> At the very end it makes a frame that is 188x46 characters large so IIUC
>> more than you asked for. Does this size figure anywhere in one of your
>> resources?
>
> No.
Do you see a mode line and a minibuffer window in that small frame.
Could you post a screenshot of it?
> I think it was
> ((outer-position 1214 . 79) (outer-size 220 . 300) (external-border-size 14 . 17) (outer-border-width . 0) (title-bar-size 0 . 32) (menu-bar-external . t) (menu-bar-size 192 . 25) (tab-bar-size 0 . 0) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 192 . 41) (internal-border-width . 0))
> but I had to resize the window to read it!
What do (frame-width) and (frame-height) get you for that frame?
Thanks, martin
prev parent reply other threads:[~2024-10-27 8:47 UTC|newest]
Thread overview: 22+ 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
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 [this message]
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=306d175c-6134-4797-a4a6-9b1ab477f62c@gmx.at \
--to=bug-gnu-emacs@gnu.org \
--cc=73244@debbugs.gnu.org \
--cc=ajh@ajhurst.org \
--cc=rudalics@gmx.at \
/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.