From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 26682@debbugs.gnu.org
Subject: bug#26682: 26.0.50; Error at startup with minibuffer-only frame
Date: Sat, 29 Apr 2017 12:30:39 +0200 [thread overview]
Message-ID: <59046B4F.3070601@gmx.at> (raw)
In-Reply-To: <59037F7C.8080107@gmx.at>
> On Windows, however, even
> with my patch, one out of ten times starting Emacs with Stefan's command
> line hangs it with the initial frame visible and I have to quit with
> C-g.
>
> More precisely, it hangs in ‘frame-notice-user-settings’ in the while
> loop below
>
> ;; MS-Windows needs this to avoid inflooping below.
> (if (eq system-type 'windows-nt)
> (sit-for 0 t))
> ;; If the frame isn't visible yet, wait till it is.
> ;; If the user has to position the window,
> ;; Emacs doesn't know its real position until
> ;; the frame is seen to be visible.
> (while (not (cdr (assq 'visibility
> (frame-parameters frame-initial-frame))))
> (sleep-for 1))
>
> and it does so always when I run Emacs under GDB. I don't yet know why
> it hangs: The request to make the frame visible is posted orderly but
> somehow SET_FRAME_VISIBLE gets never executed. Can you reproduce it?
FYI it's caused by WM_MOVE which OT1H is likely counted by the
for (count = input_signal_count + 10;
input_signal_count < count && !FRAME_VISIBLE_P (f);)
loop in x_make_frame_visible and OTOH lacks a SET_FRAME_VISIBLE (f, 1).
martin
next prev parent reply other threads:[~2017-04-29 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 17:08 bug#26682: 26.0.50; Error at startup with minibuffer-only frame Stefan Monnier
2017-04-28 8:56 ` Eli Zaretskii
2017-04-28 17:44 ` martin rudalics
2017-04-28 18:29 ` Stefan Monnier
2017-04-30 8:32 ` martin rudalics
2017-04-30 16:14 ` Stefan Monnier
2017-04-29 10:30 ` martin rudalics [this message]
2017-04-29 10:36 ` Eli Zaretskii
2017-04-30 8:32 ` martin rudalics
2017-04-30 14:16 ` Eli Zaretskii
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=59046B4F.3070601@gmx.at \
--to=rudalics@gmx.at \
--cc=26682@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.