From: "Drew Adams" <drew.adams@oracle.com>
To: <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: RE: test for a (really) visible frame? test if a frame is the only (really visible) one?
Date: Tue, 2 Mar 2010 11:32:17 -0800 [thread overview]
Message-ID: <2C2CA65FBE034922824996CFBA125A59@us.oracle.com> (raw)
In-Reply-To: <29818.128.165.0.81.1267556791.squirrel@webmail.lanl.gov>
> > 4. It is impossible to test whether a given frame is a
> > terminal frame. There is no predicate for this and no
> > frame parameter that indicates this.
>
> See `framep' (and `frame-live-p').
OK; thanks for that reminder.
But I don't think that helps with the other problems. In particular, how to
distinguish the extra, special, never seeable (but always "visible") `--daemon'
frame as such. For example, how to distinguish that from an ordinary terminal
frame, which AFAIK _will_ show if you delete the other visible frames.
It is #6 that I am really most interested in: test whether a given frame is the
sole frame visible to the eye. (#5 also, since it would presumably provide a way
to test #6.)
And the simple use case mentioned:
> Define a function to delete the selected window or, if only
> one window, the selected frame - but never delete the last
> frame visible to the eye (including when `--daemon' is used).
prev parent reply other threads:[~2010-03-02 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 18:29 test for a (really) visible frame? test if a frame is the only (really visible) one? Drew Adams
2010-03-02 19:06 ` Davis Herring
2010-03-02 19:32 ` Drew Adams [this message]
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=2C2CA65FBE034922824996CFBA125A59@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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).