From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: execvy@gmail.com, emacs-devel@gnu.org
Subject: Re: [MPS-test] scratch/igc branch (commit: 42731228d24) crashed
Date: Mon, 05 Aug 2024 18:01:59 +0200 [thread overview]
Message-ID: <m2wmkv6jrc.fsf@pro2.fritz.box> (raw)
In-Reply-To: <861q33q82c.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 05 Aug 2024 18:54:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: Eval Exec <execvy@gmail.com>, emacs-devel@gnu.org
>> Date: Mon, 05 Aug 2024 17:47:10 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > I guess no one has yet built the branch with Lucid toolkit? Maybe the
>> > scroll bars etc. in that build are not handled correctly?
>>
>> Could also be, yes.
>
> Look here (xterm.c):
>
> #ifndef USE_MOTIF
> hints_changed
> = widget_update_wm_size_hints (f->output_data.x->widget,
> f->output_data.x->edit_widget);
> #else
>
> We call widget_update_wm_size_hints with f->output_data.x->widget, but
> output_data.c->widget hides a pointer to 'struct frame':
>
> bool
> widget_update_wm_size_hints (Widget widget, Widget frame)
> {
> return update_wm_hints ((WMShellWidget) widget, (EmacsFrame) frame);
> }
>
> and update_wm_hints does:
>
> pixel_to_char_size (ew, ew->core.width, ew->core.height,
> &char_width, &char_height);
>
> which does
>
> static void
> pixel_to_char_size (EmacsFrame ew, Dimension pixel_width,
> Dimension pixel_height, int *char_width, int *char_height)
> {
> struct frame *f = ew->emacs_frame.frame;
>
> So if the frame object is moved and
> f->output_data.x->widget->emacs_frame.frame is not updated, we are
> toast, right?
Yep.
next prev parent reply other threads:[~2024-08-05 16:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 15:00 [MPS-test] scratch/igc branch (commit: 42731228d24) crashed Eval Exec
2024-08-05 15:12 ` Gerd Möllmann
2024-08-05 15:18 ` Eval Exec
2024-08-05 15:34 ` Gerd Möllmann
2024-08-05 15:20 ` Eval Exec
2024-08-05 15:45 ` Gerd Möllmann
2024-08-05 15:48 ` Eval Exec
2024-08-05 15:55 ` Eval Exec
2024-08-05 16:14 ` Eval Exec
2024-08-05 15:29 ` Eli Zaretskii
2024-08-05 15:33 ` Eval Exec
2024-08-05 15:47 ` Gerd Möllmann
2024-08-05 15:54 ` Eli Zaretskii
2024-08-05 16:01 ` Gerd Möllmann [this message]
2024-08-05 16:20 ` Pip Cet
2024-08-05 16:40 ` Pip Cet
2024-08-05 16:50 ` Eval Exec
2024-08-05 17:45 ` Eli Zaretskii
2024-08-05 18:00 ` Pip Cet
2024-08-05 18:19 ` Eli Zaretskii
2024-08-08 16:56 ` Eval Exec
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=m2wmkv6jrc.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=execvy@gmail.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).