unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Madhu <enometh@meer.net>
To: acm@muc.de
Cc: gregory@heytings.org, stefan@marxist.se, 47766@debbugs.gnu.org
Subject: bug#47766: 28.0.50; choose-completion fails
Date: Thu, 22 Apr 2021 21:34:29 +0530 (IST)	[thread overview]
Message-ID: <20210422.213429.112377311480064511.enometh@meer.net> (raw)
In-Reply-To: <YIGRQ29+yuasRia4@ACM>

*  Alan Mackenzie <acm@muc.de> <YIGRQ29+yuasRia4@ACM>
Wrote on Thu, 22 Apr 2021 15:07:47 +0000

> Or, more accurately, because the changes in that commit were incomplete.
> In particular, functions iconify-frame and make-frame-invisible were
> moving minibuffers in a way no longer consistent with the rest of Emacs.
>
> Madhu, would you please try out the following patch (which gives a couple
> of harmless warnings in compilation), and tell us whether it fixes the
> problems in your setup, or what is still not working properly.  Thanks!

Thank you.  I'm running it now and will let you know if i spot
anything.


The rest of this is not directlty related to the bug, but somewhat
related to your post on emacs-devel invisible and iconified windows.
mutter (gnome-shell) and wayland throw some more spanners into the
works - mutter does not have a concept of "iconified" it only has a
notion of "hidden". A hidden window has no "hidden" state as far as
the compositor is concerned. M-TAB/switchers would show previews of
the current state of the window. If an emacs frame iconifies itself
(gtk:gtk_window_iconify) rather than the user causing the compositing
window manager to hide it, it cannot map itself back.

I end up with something like
;; work around gnome-shell error
(defadvice make-frame-visible (around mutter-workaround (&optional frame) activate)
  (if (or (eql (frame-parameter frame 'visibility) 'icon)
	   (eql (frame-parameter frame 'visibility) nil)) ;gnome-shell40.a
      (set-frame-parameter frame 'visibility nil))
  ad-do-it)

to make make-frame-visible work.

[PS. There seem to be some other rough corners - sometimes I end up in
a recursive-edit where one cannot go back to the top-level and have to
quit emacs instead - but i haven't triggered this one in the past week
so i don't have a recipe for it.]





  reply	other threads:[~2021-04-22 16:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  5:03 bug#47766: 28.0.50; choose-completion fails Madhu
2021-04-14  8:43 ` Gregory Heytings
2021-04-20 13:25   ` Stefan Kangas
2021-04-21 13:54     ` Alan Mackenzie
2021-04-22 15:07     ` Alan Mackenzie
2021-04-22 16:04       ` Madhu [this message]
2021-05-05 15:33         ` Lars Ingebrigtsen
2021-05-06  2:46           ` Madhu
2021-05-06  8:33             ` Lars Ingebrigtsen
2021-05-06  9:55               ` Alan Mackenzie
2021-05-06 10:59             ` Alan Mackenzie

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=20210422.213429.112377311480064511.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=47766@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=gregory@heytings.org \
    --cc=stefan@marxist.se \
    /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).