unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: emacs-devel@gnu.org
Subject: Re: Add four new Modus themes to Emacs?
Date: Mon, 19 Dec 2022 15:53:26 +0000	[thread overview]
Message-ID: <87mt7j5r0p.fsf@posteo.net> (raw)
In-Reply-To: <871qow6ixb.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Mon, 19 Dec 2022 07:50:40 +0200")

Protesilaos Stavrou <info@protesilaos.com> writes:

> Hello everyone,

Hi,

> I am developing version-4 of the modus-themes.  Part of this endeavour
> is the creation of four new themes.  Originally, we had 'modus-operandi'
> (light theme) and 'modus-vivendi' (dark theme).  They are the ones that
> are shipped with Emacs since version 28.
>
> The new themes:

[...]

> All new themes are consistent with the WCAG AAA accessibility standard
> for colour contrast.
>
> Should these four new themes be added to emacs.git when I release
> version-4?  Or should I just update only 'modus-operandi' and
> 'modus-vivendi'?

My main worry is that the default theme options could get too crowded.
Then again, if we want to keep deuteranopia support, the two new
variants will have to be added... (On that topic, I still think that the
approach I suggested earlier this year would be preferable: Instead of a
separate theme or multiple options, we just need to describe the
transformations that maximise the volume of the original colour space
within the boundaries of whatever is permissible for each kind of colour
deficiency).

The alternative is having the base themes in Emacs, and if anyone wants
more then they would have to download the themes from ELPA, right?

> My plan is to finalise version-4 by the end of this month.  It contains
> lots of changes.

This might be a bit late, but I think that you were a bit too quick in
deprecating a lot of the user option, while also dropping backwards
compatibility.  Usually, an option is deprecated and users are given
hints what they have to do in the future, but everything will continue
working for now.  When I recently installed version-4, I noticed that a
number of things changed and I wasn't sure where to look to fix these
issues.  Now of course, this is just a visual theme and nothing about
Emacs breaks functionality-wise, but it would still be nice to have a
shim for now that translates old user options into the new configuration
pattern.




  parent reply	other threads:[~2022-12-19 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  5:50 Add four new Modus themes to Emacs? Protesilaos Stavrou
2022-12-19  9:12 ` Tim Cross
2022-12-19 14:51   ` Protesilaos Stavrou
2022-12-19 12:19 ` Eli Zaretskii
2022-12-19 14:44   ` Protesilaos Stavrou
2022-12-19 15:11 ` T.V Raman
2022-12-19 15:53 ` Philip Kaludercic [this message]
2022-12-19 16:33   ` Protesilaos Stavrou

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=87mt7j5r0p.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.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).