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#37079: 26.2.90 feature request; bury-frame command for desktop-wm Date: Wed, 21 Aug 2019 09:36:54 +0200 Message-ID: References: <38CF2C4B-C213-48A3-83C3-66220FB62C9F@scratch.space> <78c56b66-b46b-335e-bd4c-39ae81a21ab3@gmx.at> <0C3B5FB5-3E39-4087-9144-F5F6A71D2F10@scratch.space> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="133692"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 37079@debbugs.gnu.org To: VanL Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Aug 21 10:08:42 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 1i0Lfd-000Yan-W4 for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Aug 2019 10:08:42 +0200 Original-Received: from localhost ([::1]:44902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i0Lfc-00069s-I2 for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Aug 2019 04:08:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44309) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i0LC0-0001Rk-AW for bug-gnu-emacs@gnu.org; Wed, 21 Aug 2019 03:38:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i0LBz-0004b9-3x for bug-gnu-emacs@gnu.org; Wed, 21 Aug 2019 03:38:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53909) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i0LBy-0004b1-Vr for bug-gnu-emacs@gnu.org; Wed, 21 Aug 2019 03:38:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i0LBy-0004ZA-T0 for bug-gnu-emacs@gnu.org; Wed, 21 Aug 2019 03:38:02 -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, 21 Aug 2019 07:38:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37079 X-GNU-PR-Package: emacs Original-Received: via spool by 37079-submit@debbugs.gnu.org id=B37079.156637302817466 (code B ref 37079); Wed, 21 Aug 2019 07:38:02 +0000 Original-Received: (at 37079) by debbugs.gnu.org; 21 Aug 2019 07:37:08 +0000 Original-Received: from localhost ([127.0.0.1]:34493 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i0LB5-0004Xe-Mi for submit@debbugs.gnu.org; Wed, 21 Aug 2019 03:37:07 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:55091) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i0LB2-0004X9-IY for 37079@debbugs.gnu.org; Wed, 21 Aug 2019 03:37:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1566373015; bh=/8FLGhCBcGiN6KS3Xdvw/OQlD7BSLu9AoURsmvXNmm8=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=Q0lt2JVFSVBNoecw5WyG2txcG8Fkv06KtEKYftipqH0tuQvcvsUvwlx5/JShw+VQd ND4Jtf9wfwfve7vOPdEAIRBd4klM+GS4T8VSlZVHIZ/liIHrmQ2sDGPoDOEU2UQ5bp 0Yqobffcnu4fKCACYKTvS/SVl2rmGjSvYQ2GqhW4= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([212.95.5.108]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M1msU-1iG5sL1ZgQ-00tkNQ; Wed, 21 Aug 2019 09:36:55 +0200 In-Reply-To: <0C3B5FB5-3E39-4087-9144-F5F6A71D2F10@scratch.space> Content-Language: de-DE X-Provags-ID: V03:K1:HWGTnHghK/UpbYvAyXpi5aVuH+I6LLcGjzXJeEvgAKoGOoWA2eu iYRFTYwmGKZGTZnkFlix1yiYrcU0SiKjz+3WYVSMeBzheR8mP65fJx6OsHkuStKiG/qGriP JpyQ8q26MUAqXVkejQX1j4ZnzQ/I5t7/5WyiOGq5MjzM64gx93b/LHAhnusGTt6uWG0d3vi jn4/hR4XqEKrLQ4CXfltQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:peCnK5OyAig=:mpE9ajWgXXCJjZYJy6SQI6 e/wHTZ4YWxaecBMKbebVLne16f4tUcVVUnQ9XtXyQp8A+nG5dKw/nreClzAj9obWs5YmJ6wS1 U8quFhmJtgJiOOdXU0HZ3adLHX89+xG6gmWJLL0OjpQprock8L41qAaaP/r4q9yiltczG8xPD v3eoKCL1CJ6zjDyFS8cPrWA9B1daTARML4otEwEvPQD862HVwp9tA3EVD9id22ok9UT5UYZaU g8uakXX810HK7InWLGh7j4ZInGQ0EzTMFpTvIXBMnB6YXqY2mDTLT/wfPG8KD580d5rTBhM5O ZzRITUi285gbsNCXAI2IU7xOl9QibpZAmGs2B4m+kJVvpC6imaq0LMmqZvjrFQvNdSHtOGhV6 P5PHJvgXvncGtOJ6IExDRvHbujLoomA4tUqEW76d2mmjqLyd+Hcb7DwnIwfll4ILATQ6mbKxS eN752RO7Z0WcvtNthcJG6cTLVHaYbhDU52NEj2uMBmyyOwtEHD0BAhLmF5uIq3z2+vd0wrRlY hZfrd25pyVRsQAMIn29UvQgA+SZqmF55pz9S3P3c3csJxCK2P3pwA2Z2FofcAwCGxDBooMqcd GZeZ1oPzX6/hd7K0bgnnNi/FJJ22teHhJ9QlgbfFBLq0Tm/YbHX0udJpMLFt9ba+Zy8xQBBNG 9KcvSD1EFhb1bbX41FTApjcZlZzw7Ym3C6Wbt70t5q2Eaw5iBu1/3lkls+YAD74CIW+O91IFc uFPFWe1p73/I6t7QxwPBqJmEDBxG2mUKRNthHDYSzmXEfLjB4tOJmkRPwUYFb+ts7LkK3y/g 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:165477 Archived-At: >> What should 'bury-frame' do? In which sense would it be different >> from 'lower-frame'? How would you return-back-to a buried frame? > > The two terms are synonymous. I searched for the idea closest to > 'lower-frame' on the web and used 'bury-frame' in this feature > request for the reason that `bury' is what is done to move a buffer > to the `bottom' of a 'listing of buffers'. Whatever 'bury-buffer' does, it's effect can be fully controlled by Emacs itself. 'lower-frame' has Emacs ask the window manager to put the window of an Emacs frame at the bottom of the z-order of visible windows. Thereafter, the effect of this operation is completely with the window manager and Emacs has no control over it. > Use case: I am editing within an Emacs frame. I context switch to > another app and want to lower (or bury) the Emacs frame with a quick > keyboard shortcut. So all you want is that Emacs by default assigns a keyboard shortcut to 'lower-frame'. Which combination did you have in mind? > After completing the task at the other app which > has taken my hand to the mouse I want to continue on that lowered > Emacs frame by clicking on that. To bury the frame completely > without any part of it showing for mouse clicking to raise is a > corner case I may not want all of the time. You mean lowering the frame would continue to show parts of it not hidden by other applications' windows while minimizing the frame would not show aynthing. I still wonder why you don't just actively switch to that other application's window (with the mouse or via Alt-Tab) instead of using 'lower-frame' which would just passively reveal the window that happens to be beneath the one of the Emacs frame. martin