all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Dark mode on Windows
Date: Mon, 25 Oct 2021 14:31:45 +0200	[thread overview]
Message-ID: <878ryhjnf2.fsf@telefonica.net> (raw)
In-Reply-To: 87r1c9ybau.fsf@yahoo.com

Po Lu <luangruo@yahoo.com> writes:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> KDE and other window managers I use on GNU/Linux set themselves the
>> window decorations, not the application. Is GTK an exception to that?
>
> Yes, GTK+ 3.0 provides the ability to use a different style (such as
> Adwatia Dark) for window decorations (and GTK+ widgets in general).

That's the same I was saying about KDE.

> AFAIK that if the window does not have client-side decorations, it is
> automatically converted to use them.

Emacs has no client-side window decorations, right? More specifically,
it does not sets the background of the title frame.

>> Supporting ancient OSes is not a requirement for accepting patches that
>> implement new capabilities.
>
> IIUC, this does not just implement new capabilities, but will prevent
> Emacs from working at all on older systems.

False. Emacs has lots of features that don't work on old systems. Emacs
runs on those systems with those features disabled.

>> Of course it doesn't work on "slightly old" versions of Windows, because
>> them lack the feature, as the OP implicitly informs us when he says
>> "Windows 10 has..."
>
> Yes, but the function is not dynamically loaded.  This will cause symbol
> resolution failures on older systems.

This can be fixed, Emacs already does that on lots of places, moreso
when it runs on Windows.

>> Why such discouraging review?
>
> I wasn't trying to discourage the OP, just to help.

That was not the tone I perceived from here.




  reply	other threads:[~2021-10-25 12:31 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 [this message]
2021-10-26  5:02           ` Po Lu
2021-10-25  4:14     ` Vince Salvino
2021-10-25  4:27       ` Po Lu
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ryhjnf2.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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 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.