From: Jai Vetrivelan <jaivetrivelan@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 55543@debbugs.gnu.org
Subject: bug#55543: 29.0.50; Unintended transparency in Emacs Frame
Date: Sat, 21 May 2022 08:09:27 +0530 [thread overview]
Message-ID: <87tu9jtxr4.fsf@gmail.com> (raw)
In-Reply-To: <877d6fvf2v.fsf@yahoo.com>
On 2022-05-21, 09:39 +0800, Po Lu <luangruo@yahoo.com> wrote:
> Jai Vetrivelan <jaivetrivelan@gmail.com> writes:
>
>> Hello,
>>
>> I’ve rebuilt Emacs from master without pgtk flag and now the transparency of
>> the frame makes it’s contents unintelligible. This happens with both
>> `emacs’ and `emacs -q’ but not `emacs -Q’. I’ve attached screenshots of
>> the last two for reference.
>
> Please show the output of "xrdb -query".
┌────[ xrdb -query ]
│ *.alpha: 0.8
│ *.font: Iosevka Comfy:size=11:antialias=true
│ Xft.antialias: true
│ Xft.hinting: true
│ Xft.rgba: rgb
│ Xft.lcdfilter: lcddefault
│ Xft.hintstyle: hintslight
│ XTerm.termName: xterm-256color
│ XTerm*locale: true
│ Xterm*saveLines: 8192
│ xterm*bellIsUrgent: true
│ XTerm*cursorBlink: true
│ XTerm*on3Clicks: regex [^ ]+
│ XTerm*on4Clicks: regex .+
│ XTerm*scrollbar*thickness: 4
│ XTerm*scrollbar*thumb: black
│ xterm*foreground: #c5c8c6
│ xterm*scrollbar*foreground: #81a2be
│ xterm*background: #1d1f21
│ xterm*cursorColor: #aeafad
│ xterm*faceName: Iosevka Comfy:antialias=true
│ xterm*faceSize: 11
│ XTerm*utf8: always
│ XTerm*metaSendsEscape: true
└────
Commenting out the first line in Xresources seems to get rid of the transparency.
--
Jai Vetrivelan
next prev parent reply other threads:[~2022-05-21 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:49 bug#55543: 29.0.50; Unintended transparancy in Emacs Frame Jai Vetrivelan
2022-05-21 1:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-21 2:39 ` Jai Vetrivelan [this message]
2022-05-21 2:46 ` bug#55543: 29.0.50; Unintended transparency " 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=87tu9jtxr4.fsf@gmail.com \
--to=jaivetrivelan@gmail.com \
--cc=55543@debbugs.gnu.org \
--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.