From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: lekktu@gmail.com, 37415@debbugs.gnu.org
Subject: bug#37415: Asserting failure setting frame parameters to non-fixnum values in early-init.el
Date: Sun, 22 Sep 2019 19:43:20 +0300 [thread overview]
Message-ID: <83y2ygp9hz.fsf@gnu.org> (raw)
In-Reply-To: <c24ca6d8-0821-8c11-63c3-015da2365beb@gmx.at> (message from martin rudalics on Sun, 22 Sep 2019 10:08:53 +0200)
> Cc: 37415@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 22 Sep 2019 10:08:53 +0200
>
> When called with PARAM Qleft and ALIST Qnil x_get_arg
>
> {
> Lisp_Object tem;
>
> tem = Fassq (param, alist);
>
> if (!NILP (tem))
> ...
> XSETCAR (XCAR (tail), Qnil);
> }
> else
> tem = Fassq (param, Vdefault_frame_alist);
>
> if (NILP (tem))
> ...
>
> return Fcdr (tem);
> }
>
> returns the cdr of the 'default-frame-alist' entry for 'left' which
> can be anything. So that comment is wrong and using x_get_arg here
> probably too.
No, I don't think using x_get_arg is wrong, because we still want to
determine whether to use CW_USEDEFAULT.
> Any reason why we cannot just use f->left_pos
>
> my_create_window (struct frame * f)
> {
> MSG msg;
> static int coords[2];
>
> coords[0] = f->left_pos;
> coords[1] = f->top_pos;
> if (!PostThreadMessage (dwWindowsThreadId, WM_EMACS_CREATEWINDOW,
> (WPARAM)f, (LPARAM)coords))
> emacs_abort ();
> GetMessage (&msg, NULL, WM_EMACS_DONE, WM_EMACS_DONE);
> }
>
> like the X build does?
We cannot do this unless f->size_hint_flags are set so as to tell
w32_createwindow to use f->top_pos and/or f->left_pos. Otherwise, we
should put CW_USEDEFAULT in coords[]. IOW, how about the below?
diff --git a/src/w32fns.c b/src/w32fns.c
index 34abd02..2ae84fc 100644
--- a/src/w32fns.c
+++ b/src/w32fns.c
@@ -5421,20 +5421,28 @@ my_create_window (struct frame * f)
Lisp_Object left, top;
struct w32_display_info *dpyinfo = &one_w32_display_info;
- /* When called with RES_TYPE_NUMBER, gui_display_get_arg will return
- zero for anything that is not a number and is not Qunbound. */
- left = gui_display_get_arg (dpyinfo, Qnil, Qleft, "left", "Left",
- RES_TYPE_NUMBER);
- top = gui_display_get_arg (dpyinfo, Qnil, Qtop, "top", "Top",
- RES_TYPE_NUMBER);
- if (EQ (left, Qunbound))
- coords[0] = CW_USEDEFAULT;
- else
- coords[0] = XFIXNUM (left);
- if (EQ (top, Qunbound))
- coords[1] = CW_USEDEFAULT;
- else
- coords[1] = XFIXNUM (top);
+ if (!(f->size_hint_flags & USPosition || f->size_hint_flags & PPosition))
+ {
+ /* When called with RES_TYPE_NUMBER, and there's no 'top' or
+ 'left' parameters in the frame's parameter alist,
+ gui_display_get_arg will return zero for anything that is
+ neither a number nor Qunbound. If frame parameter alist does
+ have 'left' or 'top', they are interpreted by
+ gui_figure_window_size, which was already called, and which
+ sets f->size_hint_flags. */
+ left = gui_display_get_arg (dpyinfo, Qnil, Qleft, "left", "Left",
+ RES_TYPE_NUMBER);
+ top = gui_display_get_arg (dpyinfo, Qnil, Qtop, "top", "Top",
+ RES_TYPE_NUMBER);
+ if (EQ (left, Qunbound))
+ coords[0] = CW_USEDEFAULT;
+ else
+ coords[0] = XFIXNUM (left);
+ if (EQ (top, Qunbound))
+ coords[1] = CW_USEDEFAULT;
+ else
+ coords[1] = XFIXNUM (top);
+ }
if (!PostThreadMessage (dwWindowsThreadId, WM_EMACS_CREATEWINDOW,
(WPARAM)f, (LPARAM)coords))
next prev parent reply other threads:[~2019-09-22 16:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 22:34 bug#37415: Asserting failure setting frame parameters to non-fixnum values in early-init.el Juanma Barranquero
2019-09-17 16:01 ` Eli Zaretskii
2019-09-17 17:04 ` Juanma Barranquero
2019-09-18 7:45 ` martin rudalics
2019-09-18 12:31 ` Eli Zaretskii
2019-09-19 8:17 ` martin rudalics
2019-09-19 14:13 ` Eli Zaretskii
2019-09-20 8:13 ` martin rudalics
2019-09-20 19:08 ` Eli Zaretskii
2019-09-21 8:51 ` martin rudalics
2019-09-21 9:14 ` Eli Zaretskii
2019-09-21 10:02 ` Juanma Barranquero
2019-09-21 12:27 ` Eli Zaretskii
2019-09-22 5:54 ` Juanma Barranquero
2019-09-22 8:09 ` martin rudalics
2019-09-22 16:26 ` Eli Zaretskii
2019-09-22 8:08 ` martin rudalics
2019-09-22 16:43 ` Eli Zaretskii [this message]
2019-09-22 17:54 ` martin rudalics
2019-09-22 18:19 ` Eli Zaretskii
2019-09-23 7:32 ` martin rudalics
2019-09-23 16:35 ` Eli Zaretskii
2019-09-24 6:45 ` martin rudalics
2019-09-24 7:41 ` Eli Zaretskii
2019-09-22 8:08 ` martin rudalics
2019-09-22 16:27 ` Eli Zaretskii
2019-09-22 17:53 ` martin rudalics
2019-09-22 18:16 ` Eli Zaretskii
2019-09-23 7:32 ` martin rudalics
2019-09-23 16:08 ` Eli Zaretskii
2019-09-21 4:25 ` Juanma Barranquero
2019-09-18 2:30 ` Paul Eggert
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=83y2ygp9hz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37415@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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 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).