GNU bug report logs - #30019
26.0.90; Invalid specification of parent-frame with desktop-read

Previous Next

Full log

Message #29 received at 30019 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 30019 <at> debbugs.gnu.org, aaronjensen <at> gmail.com
Subject: Re: bug#30019: 26.0.90; Invalid specification of parent-frame with
 desktop-read
Date: Thu, 11 Jan 2018 18:07:39 +0200

> Date: Thu, 11 Jan 2018 11:54:57 +0100
> From: martin rudalics <rudalics <at> gmx.at>
> CC: aaronjensen <at> gmail.com, 30019 <at> debbugs.gnu.org
> 
> Normal minibuffer frames are top-level frames, they have no parent.
> So we have no problems with minibuffer frames because the window
> system will have created and made them visible some time before the
> first user interaction occurs.
> 
> The problem here is with child frames whose window system parent
> window can be assigned only after that parent window has been made by
> the window system and whose identity has been reported to us.

OK, so I've misinterpreted your references to minibuffer.

Then the problem is that desktop.el is trying to restore a child frame
whose parent frame's ID has not yet been reported back to us, is that
right?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.