all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 11 Jan 2018 18:07:39 +0200	[thread overview]
Message-ID: <83k1wo4bw4.fsf@gnu.org> (raw)
In-Reply-To: <5A574281.6080909@gmx.at> (message from martin rudalics on Thu, 11 Jan 2018 11:54:57 +0100)

> Date: Thu, 11 Jan 2018 11:54:57 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: aaronjensen@gmail.com, 30019@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?





  reply	other threads:[~2018-01-11 16:07 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
2018-01-11 10:54         ` martin rudalics
2018-01-11 16:07           ` Eli Zaretskii [this message]
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=83k1wo4bw4.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.