unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Vigouroux via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53745@debbugs.gnu.org
Subject: bug#53745: Toggle the visibility state of frames
Date: Sat, 05 Feb 2022 08:27:59 +0100	[thread overview]
Message-ID: <87iltthiww.fsf_-_@laposte.net> (raw)
In-Reply-To: <SJ0PR10MB54880F152BEAAF3F7624F9D1F3289@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Thu, 3 Feb 2022 16:32:40 +0000")

One could say that it’s not that obvious! At first sight, I don’t see
much point in making a frame invisible.

`make-frame-invisible' is a special command only mentionned in the Emacs
Lisp Ref. manual. The user must be able to select the frame again to
make it reappear using `make-frame-visible'. It is not clear if it is
possible to run `make-frame-visible' interactively (as a command).

So far, the only reference I have found about this topic is
`minibuffer-exit'.

#+begin_quote
`minibuffer-exit'

When this parameter is non-‘nil’, Emacs will by default make this frame
invisible whenever the minibuffer (see Minibuffers) is exited.
Alternatively, it can specify the functions ‘iconify-frame’ and
‘delete-frame’. This parameter is useful to make a child frame disappear
automatically (similar to how Emacs deals with a window) when exiting
the minibuffer.
#+end_quote
-- 
Kevin Vigouroux
Best regards





  reply	other threads:[~2022-02-05  7:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  9:23 bug#53745: [DOC] About invisible frames Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 16:32 ` bug#53745: [External] : " Drew Adams
2022-02-05  7:27   ` Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-06  4:01     ` bug#53745: Toggle the visibility state of frames Michael Heerdegen

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=87iltthiww.fsf_-_@laposte.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53745@debbugs.gnu.org \
    --cc=ke.vigouroux@laposte.net \
    /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).