From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: aaronjensen@gmail.com, 30019@debbugs.gnu.org
Subject: bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read
Date: Wed, 10 Jan 2018 17:53:05 +0200 [thread overview]
Message-ID: <83a7xl678e.fsf@gnu.org> (raw)
In-Reply-To: <5A55E900.3050503@gmx.at> (message from martin rudalics on Wed, 10 Jan 2018 11:20:48 +0100)
> Date: Wed, 10 Jan 2018 11:20:48 +0100
> From: martin rudalics <rudalics@gmx.at>
>
> >> When you put a breakpoint at the last line I suppose it's the
> >> FRAME_X_P (p) call that failed. Can you confirm that?
> >
> > Confirmed, it was FRAME_X_P (p) that came back false.
>
> In practice this means that with desktop in use I have to install some
> sort of hook or timer that triggers when the parent frame has been
> mapped and reparent the (until then probably hidden and not yet
> parented) child frame.
I don't think I understand why you need this. I thought you said that
we only need an X window when the minibuffer becomes active, or did I
misunderstand? If I did understand correctly, then this problem
sounds like something that should be worked around by avoiding the
error, not something that needs to be fixed. The parent frame will be
eventually mapped, most probably much sooner than the user uses the
minibuffer for the first time. Right?
next prev parent reply other threads:[~2018-01-10 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 2:48 bug#30019: 26.0.90; Invalid specification of parent-frame with desktop-read Aaron Jensen
2018-01-08 9:53 ` martin rudalics
2018-01-09 10:24 ` martin rudalics
2018-01-09 16:21 ` Aaron Jensen
2018-01-09 18:40 ` Eli Zaretskii
2018-01-10 10:20 ` martin rudalics
2018-01-10 15:53 ` Eli Zaretskii [this message]
2018-01-11 10:54 ` martin rudalics
2018-01-11 16:07 ` Eli Zaretskii
2018-01-11 17:06 ` martin rudalics
2018-01-11 17:56 ` Eli Zaretskii
2018-01-11 18:20 ` martin rudalics
2018-01-11 20:49 ` Eli Zaretskii
2018-01-12 8:47 ` martin rudalics
2018-01-12 9:43 ` Eli Zaretskii
2018-01-13 2:42 ` Aaron Jensen
2018-01-13 8:50 ` martin rudalics
2020-08-26 13:26 ` Lars Ingebrigtsen
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=83a7xl678e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30019@debbugs.gnu.org \
--cc=aaronjensen@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 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.