unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Håkon Flatval" <hkon20@hotmail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Support for background transparency
Date: Thu, 4 Nov 2021 19:45:03 +0000	[thread overview]
Message-ID: <PRAP251MB06889D05E9BB03A67FD23E23CF8D9@PRAP251MB0688.EURP251.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

Hi, emacs-devel!

I have implemented partial support for background transparency in Emacs. The fork, including a description in the README can be found at https://github.com/TheVaffel/emacs. This implementation has only been made for Xlib+gtk3+cairo builds.

After posting about this in the Emacs subreddit (https://www.reddit.com/r/emacs/comments/qm3tsv/i_implemented_partial_support_for_background/), it appears to me that this is a feature that is of interest to many Emacs users.

To start off, I would just like to feel the attitude towards this feature among other Emacs developers. In general, are there any with strong opinions in favor or against this feature?

As I'm completely new to the community, I'd also like some input as to how one proceeds with planning and implementation given there is interest for this to be made reality. I would be happy to work on this, but not sure I feel comfortable / knowledgable enough to do everything on my own.

Looking forward to hearing from you!

Best Regards,
Håkon Flatval

[-- Attachment #2: Type: text/html, Size: 3080 bytes --]

             reply	other threads:[~2021-11-04 19:45 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 19:45 Håkon Flatval [this message]
2021-11-04 20:06 ` Support for background transparency Eli Zaretskii
2021-11-04 20:17 ` Lars Ingebrigtsen
2021-11-27 23:01   ` Håkon Flatval
2021-11-28  0:35     ` Sv: " arthur miller
2021-11-28 13:32       ` Lars Ingebrigtsen
2021-11-28 16:04         ` Arthur Miller
2021-11-28 20:33           ` Håkon Flatval
2021-11-29  2:56             ` Arthur Miller
2021-11-28  7:41     ` Eli Zaretskii
2021-11-28  7:47       ` Po Lu
2021-11-28  8:27         ` Eli Zaretskii
2021-12-01 18:54       ` Sv: " Håkon Flatval
2021-12-09 17:13         ` Håkon Flatval
2021-12-10  0:40           ` Lars Ingebrigtsen
2022-01-19 17:26             ` Sv: " Håkon Flatval
2022-01-20  0:52               ` Po Lu
2022-01-20 19:52                 ` Sv: " Håkon Flatval
2022-01-21  0:59                   ` Po Lu
2022-01-23 13:48                     ` Håkon Flatval
2022-01-24  0:11                       ` Po Lu
2022-01-25 17:53                         ` Håkon Flatval
2022-01-26  1:00                           ` Po Lu
2022-01-24 10:22                       ` Po Lu
2022-01-25 19:47                         ` Håkon Flatval
2022-01-25 19:37                           ` Robert Pluim
2022-01-26 18:16                             ` Håkon Flatval
2022-01-26  1:05                           ` Po Lu
2022-01-26 11:11                             ` Robert Pluim
2022-01-26 18:34                             ` Håkon Flatval
2022-01-27  1:00                               ` Po Lu
2022-01-29  0:01                                 ` Håkon Flatval
2022-01-29  1:08                                   ` Po Lu
2022-01-20  9:12               ` Robert Pluim
2022-01-23 21:43                 ` Håkon Flatval
2022-01-24  9:14                   ` Robert Pluim
2022-01-25 20:00                     ` Håkon Flatval
2022-01-25 19:31                       ` Robert Pluim
2022-01-29 10:26                         ` Po Lu
2022-01-29 15:17                           ` Håkon Flatval
2022-01-30  0:53                             ` Po Lu
2021-11-28 13:41     ` Lars Ingebrigtsen
2021-11-28 15:05       ` Sv: " Håkon Flatval
2021-11-28 16:07         ` Gregor Zattler
2021-11-28 16:32         ` Lars Ingebrigtsen
2021-11-28 18:10     ` Jean Louis
2021-11-28 18:44       ` Sv: " Håkon Flatval

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=PRAP251MB06889D05E9BB03A67FD23E23CF8D9@PRAP251MB0688.EURP251.PROD.OUTLOOK.COM \
    --to=hkon20@hotmail.com \
    --cc=emacs-devel@gnu.org \
    /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).