From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Aleksandar Dimitrov <mail@aleks.bg>, 70697@debbugs.gnu.org
Subject: bug#70697: 30.0.50; Frame parameter alpha-background is ignored for fringe bitmaps & internal borders
Date: Sat, 01 Jun 2024 22:07:19 +0800 [thread overview]
Message-ID: <87a5k4kb8o.fsf@yahoo.com> (raw)
In-Reply-To: <86y17ooj45.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Jun 2024 17:03:38 +0300")
>> From: Aleksandar Dimitrov <mail@aleks.bg>
>> Date: Thu, 16 May 2024 16:26:47 +0200
>> CC: eliz@gnu.org, 70697@debbugs.gnu.org
[...]
>> When compiling Emacs with --with-toolkit=lucid, the above patch
>> works. Fringe bitmaps' backgrounds are now transparent.
>> As before, the internal borders aren't transparent.
I suppose you meant to write `--with-x-toolkit=lucid', where
alpha-background is not supported at all, so I'm very much confused as
to why this is so. Did you really configure Emacs
`--with-toolkit=lucid'? If you did, you would have been testing a GTK
build.
next prev parent reply other threads:[~2024-06-01 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 10:52 bug#70697: 30.0.50; Frame parameter alpha-background is ignored for fringe bitmaps & internal borders Aleksandar Dimitrov
2024-05-09 7:46 ` Eli Zaretskii
2024-05-09 8:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 14:26 ` Aleksandar Dimitrov
2024-06-01 14:03 ` Eli Zaretskii
2024-06-01 14:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-03 20:24 ` Aleksandar Dimitrov
2024-06-15 8:11 ` Eli Zaretskii
2024-06-15 11:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-27 7:41 ` Eli Zaretskii
2024-07-08 17:08 ` Aleksandar Dimitrov
2024-07-09 6:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-16 8:11 ` Aleksandar Dimitrov
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=87a5k4kb8o.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=70697@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mail@aleks.bg \
/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).