emacs/var/elfeed/db/data/c2/c28ccb3e48098ba507318dcf0f9ed8e348f785c8

         
         <p>I just published version <code>0.10.0</code> of the Modus themes.  These are my
highly-accessible themes for GNU Emacs.  They conform with the WCAG AAA
standard for colour contrast accessibility (a minimum contrast ratio of
7:1 between the foreground and background values).  You can find the
packages on GNU ELPA, MELPA, MELPA stable:</p>

<ul>
  <li><code>modus-operandi-theme</code> (light)</li>
  <li><code>modus-vivendi-theme</code> (dark)</li>
</ul>

<p>Below are the release notes.</p>

<hr />

<h2>Modus Operandi and Modus Vivendi version 0.10.0</h2>

<p>By Protesilaos Stavrou <a href="mailto:info@protesilaos.com">info@protesilaos.com</a> on 2020-06-24</p>

<p>This entry records the changes since version 0.9.0 (2020-06-03).  The
present release is focused on stability and internal improvements.</p>

<h2>Fixes and adjustments</h2>

<p>Basil L. Contovounisios, aka @basil-conto, (and also a contributor to
core Emacs) sent several patches that do the following:</p>

<ul>
  <li>
    <p>Fix top-level parentheses so that the results of
<code>custom-theme-set-faces</code> and <code>custom-theme-set-variables</code> are not
passed as arguments to the first <code>custom-theme-set-faces</code>.</p>
  </li>
  <li>
    <p>Fix the docstrings of the custom <code>modus-theme-*</code> faces.</p>
  </li>
  <li>
    <p>Simplify the syntax of properties assigned to each face.</p>
  </li>
  <li>
    <p>Improve the way styles are inherited by Dired and Ibuffer.</p>
  </li>
</ul>

<p>Basil also pointed out an inconsistency with regard to an unwanted
underline effect for the <code>doom-modeline-urgent</code> face in Modus Vivendi.
It was promptly removed.</p>

<p>From my part, I fixed issues 46 and 51 that concerned the way the
compiler would evaluate each theme’s palette.  The palette is now
defined as a constant.  Further information:</p>

<ul>
  <li>https://gitlab.com/protesilaos/modus-themes/-/issues/46</li>
  <li>https://gitlab.com/protesilaos/modus-themes/-/issues/51</li>
</ul>

<h2>Improvements to existing faces</h2>

<p>André Alexandre Gomes (@aadcg) provided valuable feedback and
suggestions in issue 50 on the redesign of several <code>org-mode</code> faces.</p>

<p>The thread is long and contains lots of screenshots:
https://gitlab.com/protesilaos/modus-themes/-/issues/50</p>

<p>The changes in outline:</p>

<ul>
  <li>
    <p>Org checkboxes have a subtle background which gives them a more
pronounced appearance while retaining their overall simplicity.</p>
  </li>
  <li>
    <p>Org dates use a more saturated variant of cyan than they did before.
It helps distinguish them from their context.  Especially true for
dates inside of tables.</p>
  </li>
  <li>
    <p>Org agenda dates have also undergone a slight review to match the
above.</p>
  </li>
  <li>
    <p>Org time grid now uses a more appropriate foreground colour, which has
been designed specifically for unfocused context.</p>
  </li>
  <li>
    <p>Org todo keywords use a more semantically-correct variant of red,
rather than the purple one they had before.</p>
  </li>
  <li>
    <p>Org statistics’ cookies for pending tasks use a red variant as well
rather than the previous yellow one, in the interest of consistency
and to avoid exaggerations.</p>
  </li>
</ul>

<h2>Other internal refinements</h2>

<ul>
  <li>
    <p>Subtle review of the Modus Vivendi palette.  In short, it addresses:</p>

    <ul>
      <li>
        <p>Imbalanced levels of luminance and inconsistent differences in hue
between them and their neighbouring colours (e.g. the greens between
them, and the greens next to the yellows in the context of syntax
highlighting).  The result was that they would create an undesirable
emphatic “pop out” effect when placed close to more moderate
colours.</p>
      </li>
      <li>
        <p>Differences in luminance and hue could lead to scenaria where two
colours could be conflated with each other or otherwise fail to
perform their intended function.</p>
      </li>
      <li>
        <p>The complete report is on my website:
https://protesilaos.com/codelog/2020-06-13-modus-vivendi-palette-review/</p>
      </li>
    </ul>
  </li>
  <li>
    <p>Major review of the <code>diredfl</code> faces, in the interest of improved
readability and harmony between the various colours.  This benefits
from the palette changes in Modus Vivendi, but also from a similar
review to Modus Operandi that was documented in version 0.9.0.</p>
  </li>
  <li>
    <p>Refactor the names of dedicates colours for “marking” purposes.  These
are used in Dired, Ibuffer, Proced, etc.  Then apply them consistently
throughout each theme.</p>
  </li>
  <li>
    <p>Make sure that <code>stripes</code> uses the same colours as <code>hl-line-mode</code>.</p>
  </li>
  <li>
    <p>Let symlinks use a more appropriate colour in Dired and Trashed.</p>
  </li>
  <li>
    <p>Refine the use of colour in <code>magit-tag</code>, <code>eshell-prompt</code>,
<code>message-header-name</code>, <code>log-edit-header</code>, <code>change-log-function</code>,
<code>message-mml</code>, <code>message-header-name</code>, <code>message-separator</code>.  These are
subtle (i.e. difficult) tweaks that improve the overall presentation
in context.</p>
  </li>
  <li>
    <p>Make diff indicators not use an unnecessary background when the
user-facing option for “subtle diffs” is enabled (check the README for
the exact name of this option).  This ensures consistency between the
indicators and the actual scope of the diffs.</p>
  </li>
  <li>
    <p>Add support for the <code>minibuffer-line</code> package and extend existing
support of the faces used in the built-in Emacs info pages.</p>
  </li>
</ul>

<p>My thanks to Basil and André for their contributions!</p>