unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: A GTK-only  problem when making frames invisible
Date: Sat, 04 Feb 2017 23:28:24 +0100	[thread overview]
Message-ID: <87o9yhfv5j.fsf@rosalinde> (raw)
In-Reply-To: <58964BE4.2090404@gmx.at> (martin rudalics's message of "Sat, 04 Feb 2017 22:47:16 +0100")

On Sat, 04 Feb 2017 22:47:16 +0100 martin rudalics <rudalics@gmx.at> wrote:

>> When I execute your recipe, after the make-frame-invisible invocation
>> the new frame get minimized, i.e., is only represented on the desktop as
>> an entry in the task bar (or panel in KDE terminology), and the
>> frame-visible-p invocation returns t.  Is that expected?
>
> No.  The frame should disappear from the taskbar:
>
>      On graphical displays, invisible frames are not updated and are
>      usually not displayed at all, even in a window system’s "taskbar".

I must have misinterpreted what I saw, because now after
make-frame-invisible the new frame does indeed vanish, also from the
taskbar.  Sorry for the confusion, I don't know how I thought it was
different before.  However, frame-visible-p still returns t (not
`icon').

> Can you try with an earlier version?  

I don't have an earlier build from master than from 2017-01-25, which
behaves the same.  However, with my build from emacs-25 from 2016-11-16,
frame-visible-p returns nil.

>                                       And is there any difference if, as
> a second step, you do (iconify-frame frame) instead?

This does minimize the frame to the taskbar, and frame-visible-p returns
`icon' instead of t.

Steve Berman



  reply	other threads:[~2017-02-04 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-04 17:02 A GTK-only problem when making frames invisible martin rudalics
2017-02-04 20:12 ` Stephen Berman
2017-02-04 21:47   ` martin rudalics
2017-02-04 22:28     ` Stephen Berman [this message]
2017-02-05  9:16       ` martin rudalics

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=87o9yhfv5j.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@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 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).