From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrey Listopadov <andreyorst@gmail.com>
Cc: 64630@debbugs.gnu.org
Subject: bug#64630: 30.0.50; unable to change to raise or lower a child-frame
Date: Sat, 15 Jul 2023 09:16:28 +0800 [thread overview]
Message-ID: <871qha9doz.fsf@yahoo.com> (raw)
In-Reply-To: <87edlatfup.fsf@gmail.com> (Andrey Listopadov's message of "Fri, 14 Jul 2023 23:04:22 +0300")
Andrey Listopadov <andreyorst@gmail.com> writes:
> Hello.
>
> I'm working on an alternative windowing system for Emacs that explores
> child frames as a base for windowing, instead of using splits. I've
> noticed that no matter what I do, I can't restack child-frames. Calling
> `frame-raise' or changing the `z-group' has no effect on the frames
> spawned by my window manager.
>
> The simplest possible way to test this in Emacs -Q is to eval this code
> twice:
>
> (let ((frame
> (make-frame
> `((width . 20) (height . 8)
> (parent-frame . ,(selected-frame))
> (drag-with-header-line . t)
> (undecorated . t)
> (minibuffer . nil)))))
> (set-window-parameter
> (frame-root-window frame)
> 'header-line-format
> " %b"))
>
> It will create two small child frames, and no matter what I do the order
> of frames is not changes. A friend of mine reported that it works under
> X on Emacs 28 as expected. I suspect that it may be related to the fact
> that I'm using Wayland version of GNOME Shell and a PGTK build. I will
> try to recompile Emacs later and post the results here.
This is a known limitation of PGTK builds that is a consequence of how
newer versions of GDK implement its ``client-side windows''. It was
discussed in depth last year, within another bug report, and the
consensus was that it wouldn't be fixed any time soon.
next prev parent reply other threads:[~2023-07-15 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 20:04 bug#64630: 30.0.50; unable to change to raise or lower a child-frame Andrey Listopadov
2023-07-15 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-15 6:16 ` Eli Zaretskii
2023-09-02 22:25 ` Stefan Kangas
2023-07-15 7:43 ` Andrey Listopadov
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=871qha9doz.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64630@debbugs.gnu.org \
--cc=andreyorst@gmail.com \
--cc=luangruo@yahoo.com \
/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).