all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: VanL <van@scratch.space>
To: martin rudalics <rudalics@gmx.at>
Cc: 37079@debbugs.gnu.org
Subject: bug#37079: 26.2.90 feature request; bury-frame command for desktop-wm
Date: Mon, 19 Aug 2019 19:31:13 +1000	[thread overview]
Message-ID: <0C3B5FB5-3E39-4087-9144-F5F6A71D2F10@scratch.space> (raw)
In-Reply-To: <78c56b66-b46b-335e-bd4c-39ae81a21ab3@gmx.at>


> On 19 Aug 2019, at 17:38, martin rudalics <rudalics@gmx.at> wrote:
> 
> 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'.

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.  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.

--
v.




  reply	other threads:[~2019-08-19  9:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  5:08 bug#37079: 26.2.90 feature request; bury-frame command for desktop-wm VanL
2019-08-19  7:38 ` martin rudalics
2019-08-19  9:31   ` VanL [this message]
2019-08-21  7:36     ` martin rudalics
2019-08-22  1:24       ` Glenn Morris
2019-08-22 12:36       ` VanL
2019-08-23  7:46         ` martin rudalics
2019-08-23  9:28           ` VanL
2020-01-24  0:26             ` Stefan Kangas

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=0C3B5FB5-3E39-4087-9144-F5F6A71D2F10@scratch.space \
    --to=van@scratch.space \
    --cc=37079@debbugs.gnu.org \
    --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.