From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Akira Kyle <akira@akirakyle.com>
Cc: 53018@debbugs.gnu.org
Subject: bug#53018: 29.0.50; pgtk child frame borders wont show
Date: Wed, 05 Jan 2022 10:18:39 +0800 [thread overview]
Message-ID: <87y23v7wn4.fsf@yahoo.com> (raw)
In-Reply-To: <868rvv10c7.fsf@akirakyle.com> (Akira Kyle's message of "Tue, 04 Jan 2022 17:40:40 -0700")
Akira Kyle <akira@akirakyle.com> writes:
> In GNU Emacs 29.0.50 (build 1, aarch64-unknown-linux-gnu, GTK+ Version 3.24.30, cairo version 1.16.0)
> Repository revision: ab5ee3e29e916d4009b301841e9780aad564a6a0
> Repository branch: master
> System Description: NixOS 22.05 (Quokka)
>
> Configured using:
> 'configure
> --prefix=/nix/store/0fiqa453abl4c1c28g0baqs9s274s7ff-emacs-pgtkgcc-20220103.0
> --disable-build-details --with-modules --with-x-toolkit=gtk3
> --with-cairo --with-xwidgets --with-native-compilation --with-pgtk'
>
> Window manager is sway and (pgtk-backend-display-class) is
> "GdkWaylandDisplay"
>
> Running the following lisp in emacs -Q:
>
> (add-to-list 'load-path "~/path/to/posframe")
> (require 'posframe)
> (posframe-show " *my-posframe-buffer*"
> :string "This is a test"
> :position 1
> :border-width 30
> :border-color "red")
>
>
> The child frame border look like appears for a split second before
> disappearing and it isn't colored red but inherits the default
> background color.
Thanks, should be fixed now on master. Please test.
next prev parent reply other threads:[~2022-01-05 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:40 bug#53018: 29.0.50; pgtk child frame borders wont show Akira Kyle
2022-01-05 2:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-05 5:01 ` Akira Kyle
2022-01-05 5:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y23v7wn4.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53018@debbugs.gnu.org \
--cc=akira@akirakyle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.