unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,
	28611@debbugs.gnu.org
Subject: bug#28611: 26.0.60; iconifying a child frame seems to be problematic
Date: Wed, 27 Sep 2017 10:13:13 +0200	[thread overview]
Message-ID: <59CB5D99.3050904@gmx.at> (raw)
In-Reply-To: <56961F9B-E0DE-4FF5-8C72-5B86A12A8F95@math.s.chiba-u.ac.jp>

 > Steps to reproduce:
 >
 >    1. $ emacs -Q &
 >    2. Enlarge the frame a bit by mouse.
 >    3. Type (make-frame `((parent-frame . ,(selected-frame)))) C-j
 >    4. Click the newly created child frame.
 >    5. Type (iconify-frame) C-j
 >
 > Result:
 >
 >    The child frame becomes unresponsive.
 >    The parent frame can take input, but the cursor is still hollow.
 >
 > Maybe an attempt to iconify a child frame should cause an error.

We warn about this in the Elisp manual:

    * The semantics of maximizing and iconifying child frames is highly
      window-system dependent.  As a rule, applications should never
      invoke these operations for child frames.

I'm not sure whether we should do more about this given the fact that
these operations may and should work well on other window systems.

BTW: Does ‘make-frame-visible’ invoked for the child frame make it
responsive again?

martin






  reply	other threads:[~2017-09-27  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27  1:49 bug#28611: 26.0.60; iconifying a child frame seems to be problematic YAMAMOTO Mitsuharu
2017-09-27  8:13 ` martin rudalics [this message]
2017-09-27  9:21   ` YAMAMOTO Mitsuharu
2017-09-29  8:32     ` martin rudalics
2017-10-01  8:24       ` martin rudalics
2017-10-02  0:55         ` YAMAMOTO Mitsuharu
2017-10-02 17:27         ` Glenn Morris
2017-10-02 18:37           ` Eli Zaretskii
2017-10-03  9:15             ` martin rudalics

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=59CB5D99.3050904@gmx.at \
    --to=rudalics@gmx.at \
    --cc=28611@debbugs.gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).