unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Vince Salvino <salvino@coderedcorp.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Dark mode on Windows
Date: Mon, 25 Oct 2021 12:27:48 +0800	[thread overview]
Message-ID: <8735opzq2j.fsf@yahoo.com> (raw)
In-Reply-To: <CH2PR12MB42316C78B74B53B0C9C2124AA5839@CH2PR12MB4231.namprd12.prod.outlook.com> (Vince Salvino's message of "Mon, 25 Oct 2021 04:14:23 +0000")

Vince Salvino <salvino@coderedcorp.com> writes:

> This is not a feature of emacs, rather it is a specific feature of
> Windows which is being supported (e.g. the window manager "chrome"
> around GUI emacs). Other operating systems have their own window
> managers, which actually are user-controllable, and would not require
> such a kludge in emacs :)

But in that case, the decorations can't be controlled on a per-frame
basis.  This behaviour is desirable and could potentially drive people
to use proprietary operating systems.

> I have outlined ideas for this in the README.md in my fork. It would
> probably be possible to create a separate build profile, similar to NT
> vs Cygwin, etc. That is a bit beyond my skills, and I have no way of
> testing those systems.

If you find a solution, I can help test on Windows 9x.  But first, is
there any reason `DwmSetWindowAttribute' can't be dynamically loaded,
like many other functions are on MS-Windows?



  reply	other threads:[~2021-10-25  4:27 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 22:27 Dark mode on Windows Vince Salvino
2021-10-25  1:17 ` Po Lu
2021-10-25  1:22   ` Po Lu
2021-10-25  3:25     ` Óscar Fuentes
2021-10-25  4:32       ` Po Lu
2021-10-25 12:31         ` Óscar Fuentes
2021-10-26  5:02           ` Po Lu
2021-10-25  4:14     ` Vince Salvino
2021-10-25  4:27       ` Po Lu [this message]
2021-10-25  5:20         ` Vince Salvino
2021-10-25  6:25           ` Po Lu
2021-10-25 12:37             ` Eli Zaretskii
2021-10-25 15:44               ` Vince Salvino
2021-10-25 16:34                 ` Eli Zaretskii
2021-10-25 12:15           ` Eli Zaretskii
2021-10-25 13:17       ` Eric S Fraga
2021-10-25  9:59   ` Alan Third
2021-10-25 11:55   ` Eli Zaretskii
2021-10-25 12:22     ` Stefan Monnier
2021-10-25 12:52       ` Eli Zaretskii
2021-10-25 16:52         ` Michael Albinus
2021-10-26  2:04         ` Po Lu
2021-10-26 12:10           ` Eli Zaretskii
2021-10-26 13:35             ` Po Lu
2021-10-26 14:11               ` Eli Zaretskii
2021-10-25 13:02       ` Óscar Fuentes
2021-10-25 13:28         ` Stefan Monnier
2021-10-25 13:56           ` Óscar Fuentes
2021-10-25 17:20             ` Stefan Monnier
2021-10-26  0:56     ` Po Lu
2021-10-26  1:08       ` Óscar Fuentes
2021-10-26  2:02         ` Po Lu
2021-10-26 12:09           ` Eli Zaretskii
2021-10-27  0:36             ` Po Lu
2021-10-27 12:02               ` Eli Zaretskii
2021-10-26 12:08       ` Eli Zaretskii
2021-10-27  0:37         ` Po Lu
2021-10-27 14:36   ` Richard Stallman
2021-10-27 16:28     ` Vince Salvino
2021-10-27 19:49       ` Óscar Fuentes
2021-10-28  6:19         ` Eli Zaretskii
2021-10-25 12:42 ` Óscar Fuentes
2021-10-25 15:45   ` Vince Salvino
2021-10-26  4:29 ` Vince Salvino
2021-10-26  7:32   ` Po Lu
2021-10-26 14:03     ` Eli Zaretskii

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=8735opzq2j.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=salvino@coderedcorp.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 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).