From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#36672: 27.0.50; NS build: Creating child frame leads to empty space Date: Wed, 17 Jul 2019 10:39:15 +0200 Message-ID: <3fbee9bb-22a0-643d-1fcb-dacc1685d67e@gmx.at> References: <04CF7A6F-C1E7-4FE5-B648-8DA8CBD3B1ED@gmail.com> <20190716192822.GA63701@breton.holly.idiocy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="224441"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36672@debbugs.gnu.org To: Alan Third , Andrii Kolomoiets Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Jul 17 10:40:10 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hnfTt-000wGL-2R for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Jul 2019 10:40:09 +0200 Original-Received: from localhost ([::1]:55102 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnfTs-0007s1-5L for geb-bug-gnu-emacs@m.gmane.org; Wed, 17 Jul 2019 04:40:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48894) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnfTp-0007ru-Hs for bug-gnu-emacs@gnu.org; Wed, 17 Jul 2019 04:40:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnfTn-00035I-Lq for bug-gnu-emacs@gnu.org; Wed, 17 Jul 2019 04:40:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42691) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnfTm-00033e-1g for bug-gnu-emacs@gnu.org; Wed, 17 Jul 2019 04:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hnfTl-0006Zu-Qc for bug-gnu-emacs@gnu.org; Wed, 17 Jul 2019 04:40:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 Jul 2019 08:40:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36672 X-GNU-PR-Package: emacs Original-Received: via spool by 36672-submit@debbugs.gnu.org id=B36672.156335277925242 (code B ref 36672); Wed, 17 Jul 2019 08:40:01 +0000 Original-Received: (at 36672) by debbugs.gnu.org; 17 Jul 2019 08:39:39 +0000 Original-Received: from localhost ([127.0.0.1]:51509 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hnfTM-0006Z0-7f for submit@debbugs.gnu.org; Wed, 17 Jul 2019 04:39:36 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:52741) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hnfTI-0006Yl-Tb for 36672@debbugs.gnu.org; Wed, 17 Jul 2019 04:39:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1563352755; bh=ClYDSybcN5xBd4gud70SUvl0tAuFmnnQwJWJXHly8Jw=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=lnmuGjR/qO/dbuZlGjzajOkGuJydSHxXOPc/SPqYUvcU/K17u8SyqZxD+Xjyn99TJ e60zUAGarbArbSIZMh9NGHQsN2EbkSlxpqgARJPen3/xDTSopBDurhqoRdrY/igmmO g1Uc7WvhjmxW1vTm5cFO+MIgfZExpzao7yBPWIR4= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([212.95.5.9]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LhCDT-1iGxrY1IAB-00oSvB; Wed, 17 Jul 2019 10:39:15 +0200 In-Reply-To: <20190716192822.GA63701@breton.holly.idiocy.org> Content-Language: de-DE X-Provags-ID: V03:K1:xKn3Rwn2QA2zu2ONr2mXmNeCB89lT4zkU4dPeu46Rc1E5Kp3XOr +HNqOcQmnrmA8Qh+v2Dh6gOHA+MalvW+502PhdbDJH0pelxyQJHUe/pyFEsLxtG6LPnyh96 j/cohoclhSrR2NSV4F2hQtFWgBnvBGb+NkhoIwysuREH9+cXBIDU46nD1cdH56cSOY/z5aU ijh9SAPdE8H8SBo0uiMjg== X-UI-Out-Filterresults: notjunk:1;V03:K0:m54Xb7QQLx4=:nO841L7z7wZx2KcmtYdJua Jfj1LpHLIHTgorHcKyIltQ6YZ8M5gSOAajmXT1toUHr4+Iga1LfrxA0KWHtNZCGkXsbPES9CB cJchonvwqwWHJSTWv6XaOzXGhgDe70tV2L6QK7zwtFfnZTEuWDPejeJufYkDVuG5Aqw+aqRXT qNWkyWHLiU2/naOh8YWq+1Jd5S1yEDQyNkCoBMBupeYGPf5UqgtlVedCeQNlr8VupcsxhZ6d0 Rbq/uszDjVztkzlebWTa+q/CBCtccYks8EuQClkY5iWn2R2m5IvmVqKGJ+q8IUu8TEyGs59Cf qkZ+GzQcdnT3rSUMbUpacZhzHBQEVESV+CwqhucsQaXLblv64+A7ueeHu20EeXqiO8/SvnAZW YDwBD8BdieZyGhkXAL3ZCFlzsMMrtkxpWhREYspDmh/uQuDbzeLCaAz+eLuoKFubqv7jd/fWJ UgLQDDZ6WRqUADX/wKsebQjwHlF0KYtYUBhJBjgiVsmwrTXtBcTRjoPbEthku7ickarL3UFGQ qo7PvktJGnS5fcZFw7LJEu3nPs2MKqxVuMGFNJ6j7273syPXrInvcZwa0ATUfgOhNYg/CIXNa BOe0PJ/eGAmBDRJqSSLoo2EbfQu/Mkz9jmQDOuLGLfpY90GSONhEFfi5e4J/t0AUTz74nPBIt 2o7xBmQ1NigJ0ZstTyU5/JUVbxWFb2Sz4EJeXZ58k/Ojoel5ZrAMuDFBRh+8+h/MepQ9pS829 98ACmOvaNMdA9B8MK3lvLjL4Vua2gulA5QFizF/7zohQ6rdZXKH4Fil8d/aKnDuqTuB+eUHo X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:163224 Archived-At: >> Assume there are only one space - Desktop >> 1. emacs -Q >> 2. M-x toggle-frame-fullscreen >> Now there are two spaces - Desktop and *scratch* >> 3. eval (make-frame `((parent-frame . ,(window-frame)))) >> Now there are three spaces: >> - Desktop >> - Empty space named *scratch* with emacs menu >> - *scratch* with emacs frames but without menu > > I hit C-x C-c at this point to exit Emacs and it completely crashed my= > session. Not great... No backtrace? It sounds already strange that one apparently gets two spaces with the same name "*scratch*" here. Do things return to "normality" when one deletes the child frame before trying to exit Emacs? BTW, does maximizing a frame run into similar problems? > The patch looks good to me, Does it work with two child frames of the same parent? > but lets see if we can find solutions to > these other issues. To be honest, given that Apple don=E2=80=99t provi= de any > way to properly deal with spaces, I=E2=80=99d expect this stuff to be = handled > sensibly by default, but I guess that=E2=80=99s too much to ask. > >> 1. Removing parent-frame property leaves the frame is same space: >> >> (let ((new-frame (make-frame `((parent-frame . ,(window-frame)))))) >> (modify-frame-parameters new-frame `((parent-frame . nil)))) >> >> Maybe child frame must go fullscreen if ex-parent frame is in >> fullscreen. Does making it fullscreen then give it a separate menu? Note also that the new parent could be another frame (even a child frame). > I suppose the best thing to do would be to move it onto the first > space, but there=E2=80=99s no API for that, apparently. What happens when one sets 'parent-frame' to nil and removes the 'NSWindowCollectionBehaviorFullScreenAuxiliary' simultaneously? > Going fullscreen seems > like a reasonable work=E2=80=90around to me. > >> 2. Setting parent frame after frame creation: >> >> (let ((frame (window-frame)) >> (new-frame (make-frame))) >> (modify-frame-parameters new-frame `((parent-frame . ,frame)))) > > What do you see happening in this case? I=E2=80=99ve got spaces turned= on and > everything I do just seems to create a new fullscreen space (except > when it crashes my session). Can't one set the 'NSWindowCollectionBehaviorFullScreenAuxiliary' just as with the initial frame here? martin