From: Garklein <garklein97@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 73401@debbugs.gnu.org
Subject: bug#73401: [PATCH] Make window dividers and internal border respect alpha background
Date: Wed, 11 Dec 2024 15:51:16 -0500 [thread overview]
Message-ID: <CALp=Ck=q2gY4Mn46RJH4Y4X=cZYA4SjCGk4S6jfbxSSN1B0rhw@mail.gmail.com> (raw)
In-Reply-To: <86cyid81ea.fsf@gnu.org>
Any updates on this patch?
On Sat, Nov 30, 2024 at 5:24 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Garklein <garklein97@gmail.com>
> > Date: Sat, 23 Nov 2024 16:56:26 -0500
> > Cc: Eli Zaretskii <eliz@gnu.org>, 73401@debbugs.gnu.org
> >
> > Here is a patch that adds this option as a frame parameter.
> >
> > I hope I did everything correctly, but I have never worked with the
> > Emacs C source before, so I probably made some mistakes in style or
> > logic.
> >
> > Also, should this be factored out so that `border-alpha-background' is
> > its own parameter? In that case, a lot of functions would need to be
> > changed (the `respect-alpha-background' parameter in many xterm.c
> > functions would probably be changed to just a `double alpha` or
> > something like that). I am up for that, but I'm not sure if it would
> > be a helpful change.
> >
> > Please let me know how it looks!
>
> Po Lu, any comments?
prev parent reply other threads:[~2024-12-11 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 18:25 bug#73401: [PATCH] Make window dividers and internal border respect alpha background Garklein
2024-09-28 10:20 ` Eli Zaretskii
2024-09-28 10:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 19:37 ` Garklein
2024-10-12 11:23 ` Eli Zaretskii
2024-10-13 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 21:56 ` Garklein
2024-11-30 10:24 ` Eli Zaretskii
2024-12-11 20:51 ` Garklein [this message]
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='CALp=Ck=q2gY4Mn46RJH4Y4X=cZYA4SjCGk4S6jfbxSSN1B0rhw@mail.gmail.com' \
--to=garklein97@gmail.com \
--cc=73401@debbugs.gnu.org \
--cc=eliz@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.