branch: externals/modus-themes
commit b4ef90bb950b820a3bf316d7b212320a5b2f84d7
Author: Protesilaos Stavrou <i...@protesilaos.com>
Commit: Protesilaos Stavrou <i...@protesilaos.com>
Update to version 4.2.0
---
CHANGELOG.org | 330 +++++++++++++++++++++++++++++++++++++++++++++++++-
doc/modus-themes.info | 269 ++++++++++++++++++++--------------------
doc/modus-themes.org | 42 +++----
modus-themes.el | 2 +-
4 files changed, 475 insertions(+), 168 deletions(-)
diff --git a/CHANGELOG.org b/CHANGELOG.org
index df2325a1aa..805599b748 100644
--- a/CHANGELOG.org
+++ b/CHANGELOG.org
@@ -15,6 +15,326 @@ For further details, please consult these additional
resources:
+ Manual :: <https://protesilaos.com/emacs/modus-themes>
+ Screenshots :: <https://protesilaos.com/emacs/modus-themes-pictures>
+* 4.2.0
+:PROPERTIES:
+:CUSTOM_ID: h:29370d83-23c4-415b-afbf-ad85d4296c86
+:END:
+
+** I won a Google award for the Modus themes
+:PROPERTIES:
+:CUSTOM_ID: h:1ffc8660-511d-4fa8-aff4-11da8246a186
+:END:
+
+Report here: <https://protesilaos.com/codelog/2023-05-25-emacs-google-award/>.
+
+This is not a "change" per se, but it is worth documenting here. It
+shows how important accessibility can be in empowering people to use
+their computer and, in our case, to exercise their software freedoms.
+
+The Modus themes tend to one aspect of accessibility. They do not
+exhaust the topic, though they should at least raise awareness about
+the significance of tending to the usability needs of everyone. The
+effort I put into documenting the themes (and my other packages)
+should be understood in this light as a means of helping people enjoy
+their software freedom by learning how to use and extend the program
+in question.
+
+** New tritanopia-optimised themes
+:PROPERTIES:
+:CUSTOM_ID: h:b92706b0-9d53-4015-8916-9db3c0c87068
+:END:
+
+I have created a pair of light and dark themes that are intended for
+people with blue-yellow colour deficiency (tritanopia). These are
+~modus-operandi-tritanopia~ (light) and ~modus-vivendi-tritanopia~
+(dark). Screenshots of all the Modus themes are available on my
+website: <https://protesilaos.com/emacs/modus-themes-pictures>.
+
+The entire collection is now described in the manual as follows:
+
+#+begin_quote
+The Modus themes consist of eight themes, divided into four subgroups.
+
+- Main themes :: ~modus-operandi~ is the project's main light theme,
+ while ~modus-vivendi~ is its dark counterpart. These two themes are
+ part of the project since its inception. They are designed to cover
+ a broad range of needs and are, in the opinion of the author, the
+ reference for what a highly legible "default" theme should look
+ like.
+
+- Tinted themes :: ~modus-operandi-tinted~ and ~modus-vivendi-tinted~
+ are variants of the two main themes. They slightly tone down the
+ intensity of the background and provide a bit more color variety.
+ ~modus-operandi-tinted~ has a set of base tones that are shades of
+ light ochre (earthly colors), while ~modus-vivendi-tinted~ gives a
+ night sky impression.
+
+- Deuteranopia themes :: ~modus-operandi-deuteranopia~ and its
+ companion ~modus-vivendi-deuteranopia~ are optimized for users with
+ red-green color deficiency. This means that they do not use red and
+ green hues for color-coding purposes, such as for diff removed and
+ added lines. Instead, they implement colors that are discernible by
+ users with deueteranopia or deuteranomaly (mostly yellow and blue
+ hues).
+
+- Tritanopia themes :: ~modus-operandi-tritanopia~ and its counterpart
+ ~modus-vivendi-tritanopia~ are optimized for users with blue-yellow
+ color deficiency. The idea is the same as with the deuteranopia
+ variants: color coding relies only on hues that are accessible to
+ people with tritanopia or tritanomaly, namely, shades of red and
+ cyan.
+#+end_quote
+
+** Recalibrated the "graph" colours in all themes
+:PROPERTIES:
+:CUSTOM_ID: h:60bb2797-2db6-4d47-9d27-7d1f32291707
+:END:
+
+The new palette subset improves the contrast of all the relevant
+colours when presented side-by-side. These are most notably used by
+the ~org-habit~ consistency graph, which is displayed in the Org
+agenda. The deuteranopia and tritanopia themes have their own bespoke
+colours for this purpose, due to their specific requirements for
+colour coding (e.g. they cannot use green).
+
+** Faces or face groups
+:PROPERTIES:
+:CUSTOM_ID: h:4b68159e-d998-4781-b202-74a3dcc8ae8e
+:END:
+
+- Introduced a subtle 3D effect for clickable buttons, replacing the
+ previous 2D design. I realised the flat style creates ambiguity
+ between the button and the text fields. This happens, for example,
+ with =M-x customize-variable= for ~org-capture-templates~ which has
+ lots of button and text field combinations. The added sense of
+ depth helps with the usability of these buttons because it makes
+ them unambiguous. Personally, I prefer the 2D approach, but here we
+ have a trade-off between usability and aesthetics. According to
+ what I state in the manual:
+
+ #+begin_quote
+ If there arises an inescapable trade-off between usability and
+ stylistic considerations, we will always opt for the former.
+ #+end_quote
+
+- Refashioned the ~whitespace-mode~ to be much more subtle and added
+ the concomitant semantic colour mappings.
+
+ The previous style involved the use of a dim grey background for
+ each invisible character. While this is was good to spot invisible
+ characters quickly, it was a major hindrance for users who want to
+ run ~whitespace-mode~ at all times (e.g. for the Python programming
+ language which is space-sensitive).
+
+ We thus remove the backgrounds by default but provide the option to
+ reinstate them via palette overrides (as documented at length in the
+ manual). To this end, we have two new semantic colour mappings for
+ ordinary space, its invisible characters, as well as space errors.
+
+ Thanks to Christian Tietze and Oliver Epper for their feedback in
+ issue 80 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/issues/80>.
+
+- Applied a more subtle background for faces ~menu-bar-mode~,
+ ~tool-bar-mode~, ~scroll-bar-mode~. They do not need to stand out
+ so much because the toolkit already takes care of that. Also, we do
+ not want to dillute the semantic value of either ~bg-tab-bar~ or
+ ~fringe~ palette colour mappings that I was wrongly using before in
+ this context. Note that those faces may not apply, depending on the
+ underlying tool kit. For example, I encounter them with the Lucid
+ build of Emacs, though not with the GTK one.
+
+- Fix the critical typo of 'widget-buton', which prevented the actual
+ ~widget-button~ face from being affected by the themes. Thanks to
+ Steve Downey for pointing it out in issue 73 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/issues/73>.
+
+- Added support for the ~disk-usage~ package. It is made to look like
+ Dired, to the extent possible. Thanks to Nacho Barrientos for the
+ patch: <https://lists.sr.ht/~protesilaos/modus-themes/patches/39822>.
+ The change is small and does not require copyright assignment to the
+ Free Software Foundation.
+
+- Made the ~eglot-diagnostic-tag-unnecessary-face~ look like a
+ warning. By default it inherits the ~shadow~ face, which makes it
+ counter-intuitive as it dims the text instead of bringing it to our
+ attention. The intent of ~eglot-diagnostic-tag-unnecessary-face~ is
+ to highlight unused symbols, so this is better presented as a
+ warning.
+
+ Thanks to Augusto Stoffel for bringing this matter to my attention.
+ This was done via a private channel and the information is shared
+ with permission.
+
+- Changed the ~smerge-markers~ to inherit from ~diff-header~ instead
+ of ~diff-heading~. Thanks to Steve Downey for the contribution.
+ This was done in pull request 74 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/pull/74>. The change
+ is small and does not require copyright assignment to the Free
+ Software Foundation.
+
+- Added support for the ~jinx~ package. This was originally done by
+ Tomasz Hołubowicz in pull request 71 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/pull/71>. The change
+ is small and does not require copyright assignment to the Free
+ Software Foundation. I then modified it to make the underlines look
+ like warnings instead of errors. This is because of how the package
+ works: it automatically highlights misspellings in the visible
+ portion of the buffer. There are cases where this results in a very
+ intense presentation, which can be distracting. We want to reduce
+ the overall intensity and not draw too much attention to those
+ highlights.
+
+- Extended coverage of Org to the new ~org-agenda-calendar-daterange~
+ face (part of Org version 9.7). Thanks to Gautier Ponsinet for the
+ patch, which I received via a private channel. The change is small
+ and does not require copyright assignment to the Free Software
+ Foundation. In addition to this, I introduced a new semantic colour
+ mapping in the themes' palette called ~date-range~. This can be
+ used with the palette overrides, which are documented at length in
+ the manual (there are lots of copy-pastable examples as well).
+
+- Supported all of the new faces of the built-in ~proced~ package.
+ These are part of Emacs 29 and make the ~proced~ buffers more
+ colourful, subject to the user option ~proced-enable-color-flag~.
+ As always, the themes strive to avoid exaggerations, meaning that I
+ apply colour with restraint: not all faces need to stand out.
+
+- Included the ~rst-mode~ in the list of explicitly supported
+ packages, making its heading look like those of Org, Markdown, etc.
+ Thanks to David Edmondson for the patch:
+ <https://lists.sr.ht/~protesilaos/modus-themes/patches/40625>. I
+ believe David has already assigned copyright to the Free Software
+ Foundation, though this patch is small anyway.
+
+- Covered all the new faces of the built-in ~flymake~ package. These
+ concern the inline feedback messages (Emacs 30) as well as those
+ that appear in the echo area (Emacs 29). The former are subject to
+ the user option ~flymake-show-diagnostics-at-end-of-line~.
+
+- Reduced the intensity of the ~which-key~ prefix descriptions. Those
+ are the keymaps that displayed by ~which-key~ to hint that typing
+ the given key will open a new ~which-key~ page with more keys.
+
+- Configured new ~vundo-saved~ and ~vundo-last-saved~ faces of the
+ ~vundo~ package. They are designed to be easy to read, without
+ going over-the-top. Thanks to Nicolas Semrau for bringing this
+ matter to my attention in issue 79 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/issues/79>.
+
+- Removed the deprecated ~consult-preview-cursor~ face and made the
+ requisite adjustments to the ~consult~ faces. This was done in
+ commit =267b0c9= of the Consult Git repository. Discussed here:
+ <https://github.com/minad/consult/issues/764#issuecomment-1537491625>.
+
+- Instructed the ~shr-selected-link~ face of the built-in ~shr~
+ package to use a "mark selection" style instead of the semantically
+ incorrect "intense red" it had before. This change is helpful for
+ those who override the palette of their Modus theme of choice, while
+ it also allows us to have varied colours depending on the
+ requirements of each theme (e.g. deuteranopia/tritanopia compared to
+ the defaults).
+
+- Did the same as above, mutatis mutandis, for the faces
+ ~transient-disabled-suffix~, ~web-mode-error-face~,
+ ~erc-dangerous-host-face~, ~aw-minibuffer-leading-char-face~,
+ ~binder-sidebar-highlight~, ~binder-sidebar-missing~,
+ ~image-dired-thumb-flagged~, ~image-dired-thumb-mark~,
+ ~info-menu-star~, ~rainbow-delimiters-mismatched-face~,
+ ~evil-ex-substitute-matches~, ~iedit-occurrence~,
+ ~iedit-read-only-occurrence~, ~pgtk-im-0~, ~dired-narrow-blink~.
+
+- Enhanced the ~image-dired~ mark faces with a box border, as the use
+ of a background alone can be obscured by the underlying image
+ thumbnail, depending on its figures/colours.
+
+- Removed the backgrounds from the ~powerline-evil~ faces and
+ simplified their overral presentation in the interest of
+ maintainability. The old styles were hard to predict and test.
+ There could easily be conflicts, such as if the user would override
+ the colours of the mode line.
+
+- Ensured that ~diary~ and ~holiday~ colours are distinct and legible,
+ without being too intense.
+
+** Changes to the manual or other documentation
+:PROPERTIES:
+:CUSTOM_ID: h:d3c12dd0-4231-420b-a212-b6bd571c5c34
+:END:
+
+- Updated the doc string of the primary customisation group defined by
+ the themes to reflect the support for the case of tritanopia.
+
+- Included links to the web page of the manual and the one with the
+ sample pictures in the customisation groups. Those links appear in
+ the various Custom UI buffers.
+
+- Introduced an annotation function for all commands that involve
+ minibuffer completion. The annotations display the one-line
+ description of each theme, making it easier for a user to pick their
+ preferred choice (e.g. when using the ~modus-themes-select~
+ command).
+
+- Defined semantic colour mappings for "marks". These are used by
+ ~dired~, ~trashed~, ~proced~, and others. These is no change to the
+ default appearance of what users are already familiar with, though
+ it is now possible to override those styles.
+
+- Complemented the subset of semantic colour mappings for
+ errors/warnings with "prominent" variants. Those employ a
+ background and foreground combination. They are used in all sorts
+ of contexts, such as for fringe errors (~flymake~, ~flycheck~, ...),
+ ~query-replace~, ~isearch-fail~, and others.
+
+- Wrote sample code on how to add "padding" to the Emacs frame and the
+ space between the Emacs windows. This makes for a presentation that
+ some users find easier to work with.
+
+- Corrected the sample code for ~git-gutter~ to use the appropriate
+ symbols from the theme palette. Thanks to Christian Tietze for the
+ patch: <https://lists.sr.ht/~protesilaos/modus-themes/patches/40354>.
+ The change is small and does not require copyright assignment to the
+ Free Software Foundation.
+
+- Removed ~moody~ from the list of packages explicitly supported by
+ the themes. We stopped supporting it since version 4 that removed
+ the relevant user option for the mode line. The idea is that the
+ mode line is better handled by the user without interference from
+ the theme, due to the number of options available (and how brittle
+ those can be when interacting with unpredictable face definitions).
+ Thanks to Nicolas De Jaeghere for reminding me to remove ~moody~
+ from the manual:
+
<https://lists.sr.ht/~protesilaos/modus-themes/%3Cypi9jzyclqxy.fsf%40gmail.com%3E#%3c87jzybdgg1....@dejaeghe.re%3E>.
+
+** Miscellaneous
+:PROPERTIES:
+:CUSTOM_ID: h:7240990a-2b4d-442c-a15c-84c8d8b26622
+:END:
+
+- Added two new preset palette overrides to make the overall
+ presentation "warmer" or "cooler". Those are called
+ ~modus-themes-preset-overrides-warmer~ and
+ ~modus-themes-preset-overrides-cooler~, respectively. The manual
+ explains how those presets can be used. I suggest the user does not
+ add such overrides if they intend to load any of the deuteranopia or
+ tritanopia themes, due to the specific requirements of their design.
+
+- Refined the deuteranopia yellows for warnings, errors, and comments.
+ These otherwise slight adjustments make it considerably easier to
+ tell apart distinct elements that may be positioned close together.
+
+- Tweaked the deuteranopia semantic colour mappings for emails. The
+ subject line use a more appropriate colour value, while level 3
+ quotes stand out a bit more than they did before, without being
+ needlessly intense.
+
+- Arranged for the ~modus-themes-load-theme~ function return the value
+ of the =THEME= argument it accepts. The intent is to allow other
+ functions that call this one to capture the return value for their
+ purposes (such as with a ~let~ binding). Thank to Oliver Epper for
+ the feedback in issue 78 on the GitHub mirror:
+ <https://github.com/protesilaos/modus-themes/issues/78>.
+
* 4.1.0
:PROPERTIES:
:CUSTOM_ID: h:d028f117-8a74-4c0c-b838-9f6bf2b43c19
@@ -141,7 +461,7 @@ and the information is shared with permission.
~consult~ package. We use the ~shadow~ face in all interfaces where
line numbers are contextual information (Occur, Grep,...). With
Consult, this was not the case for commands like ~consult-line~.
-
+
Thanks to Daniel Mendler (also known as @minad) for bringing this
matter to my attention:
<https://lists.sr.ht/~protesilaos/ef-themes/%3Cb03413a6-cb77-615d-145d-db4eb710bfca%40daniel-mendler.de%3E>.
@@ -201,7 +521,7 @@ and the information is shared with permission.
weight only when the user option ~modus-themes-bold-constructs~ is
set to a non-nil value. Thanks to Marko Kocic for reporting an
issue that brought this matter to my attention:
-
+
-
<https://lists.sr.ht/~protesilaos/modus-themes/%3C35588839.256749.1673272214728%40office.mailbox.org%3E>
-
<https://lists.sr.ht/~protesilaos/modus-themes/%3C874jszvk5g.fsf%40protesilaos.com%3E>
-
<https://lists.sr.ht/~protesilaos/modus-themes/%3C87ilhfu101.fsf%40protesilaos.com%3E>
@@ -278,10 +598,10 @@ and the information is shared with permission.
contribution. Sergey's contribution is within the ~15 line limit
and thus does not require copyright assignment to the Free Software
Foundation.
-
+
This was done in merge request 59 on the GitLab mirror:
<https://gitlab.com/protesilaos/modus-themes/-/merge_requests/59>.
-
+
The prepatory discussion took place in issue 310 on the same mirror:
<https://gitlab.com/protesilaos/modus-themes/-/issues/310>.
@@ -290,7 +610,7 @@ and the information is shared with permission.
Kiraly for informing me about the fact that the ~:bind~ keyword
delays the load of the package until the given command is invoked:
<https://github.com/protesilaos/modus-themes/pull/67>.
-
+
Streamlining the configuration makes it easier for me to propose one
set of basic configurations without the need to know what a
configuration macro is doing behind the scenes.
diff --git a/doc/modus-themes.info b/doc/modus-themes.info
index 30dae43db4..274dfc5302 100644
--- a/doc/modus-themes.info
+++ b/doc/modus-themes.info
@@ -43,11 +43,11 @@ customization options for the Modus themes, and provides
every other
piece of information pertinent to them.
The documentation furnished herein corresponds to stable version
-4.1.0, released on 2023-02-22. Any reference to a newer feature which
+4.2.0, released on 2023-05-30. Any reference to a newer feature which
does not yet form part of the latest tagged commit, is explicitly marked
as such.
- Current development target is 4.2.0-dev.
+ Current development target is 4.3.0-dev.
• Package name (GNU ELPA): ‘modus-themes’
• Official manual: <https://protesilaos.com/emacs/modus-themes>
@@ -265,9 +265,8 @@ Tritanopia themes
‘modus-vivendi-tritanopia’ are optimized for users with blue-yellow
color deficiency. The idea is the same as with the deuteranopia
variants: color coding relies only on hues that are accessible to
- people with tritanopia or tritanomaly.
-
- [ The tritanopia themes are part of 4.2.0-dev. ]
+ people with tritanopia or tritanomaly, namely, shades of red and
+ cyan.
To ensure that users have a consistently accessible experience, the
themes strive to achieve as close to full face coverage as possible,
@@ -277,7 +276,7 @@ Face coverage::).
The overarching objective of this project is to always offer
accessible color combinations. There shall never be a compromise on
this principle. If there arises an inescapable trade-off between
-readability and stylistic considerations, we will always opt for the
+usability and stylistic considerations, we will always opt for the
former.
Starting with version 0.12.0 and onwards, the themes are built into
@@ -1236,8 +1235,6 @@ variable is ‘THEME-NAME-palette-overrides’, thus yielding:
• ‘modus-vivendi-tritanopia-palette-overrides’
- [ The tritanopia themes are part of 4.2.0-dev. ]
-
Theme-specific overrides take precedence over the shared ones. It is
strongly advised that shared overrides do NOT alter color values, as
those will not be appropriate for both dark and light themes. Common
@@ -1393,9 +1390,6 @@ places. Colors stand out more and are made easier to
spot.
;; Or:
(setq modus-themes-common-palette-overrides
modus-themes-preset-overrides-warmer)
- [ The “warmer” and “cooler” preset overrides are part of 4.2.0-dev.
-]
-
Note that the user is not limited to those presets. The system of
overrides we provide makes it possible to tweak the value of each
individual named color and to change how values are assigned to semantic
@@ -2884,10 +2878,9 @@ for palette overrides. Else it reads only the default
palette.
*note Option for palette overrides: Palette overrides.
- With optional ‘THEME’ as a symbol among ‘modus-themes-items’, use the
-palette of that item. Else use the current Modus theme. [As part of
-4.2.0-dev, the ‘modus-themes-items’ has an alias called
-‘modus-themes-collection’.]
+ With optional ‘THEME’ as a symbol among ‘modus-themes-items’ (alias
+‘modus-themes-collection’), use the palette of that item. Else use the
+current Modus theme.
If ‘COLOR’ is not present in the palette, this function returns the
‘unspecified’ symbol, which is safe when used as a face attribute’s
@@ -3983,7 +3976,7 @@ have lots of extensions, so the “full support” may not be
100% true…
• dired-narrow
• dired-subtree
• diredfl
- • disk-usage [Part of 4.2.0-dev]
+ • disk-usage
• display-fill-column-indicator-mode
• doom-modeline
• ediff
@@ -4049,8 +4042,8 @@ have lots of extensions, so the “full support” may not be
100% true…
• ivy*
• ivy-posframe
• jira (org-jira)
- • jit-spell [Part of 4.2.0-dev]
- • jinx [Part of 4.2.0-dev]
+ • jit-spell
+ • jinx
• journalctl-mode
• js2-mode
• julia
@@ -4102,7 +4095,7 @@ have lots of extensions, so the “full support” may not be
100% true…
• powerline
• prism (*note Note for prism.el: Note for prism.)
• prescient
- • proced [Expanded as part of 4.2.0-dev.]
+ • proced
• prodigy
• pulse
• pyim
@@ -4115,7 +4108,7 @@ have lots of extensions, so the “full support” may not be
100% true…
• rg (rg.el)
• ripgrep
• rmail
- • rst-mode [Part of 4.2.0-dev.]
+ • rst-mode
• ruler-mode
• sesman
• shell-script-mode
@@ -6144,124 +6137,124 @@ B.3 Concept index
Tag Table:
Node: Top874
Node: Overview8129
-Node: How do the themes look like10920
-Node: Learn about the latest changes11279
-Node: Installation11667
-Node: Install manually from source12597
-Node: Install from the archives13422
-Node: Install on GNU/Linux14021
-Node: Debian 11 Bullseye14514
-Node: GNU Guix14924
-Node: Dealing with byte compilation errors15207
-Node: Enable and load16365
-Node: The require-theme for built-in Emacs themes19219
-Node: Sample configuration with and without use-package20339
-Node: Differences between loading and enabling23250
-Node: Customization options25288
-Node: Custom reload theme29036
-Node: Disable other themes29944
-Node: Bold constructs31124
-Node: Italic constructs31961
-Node: Mixed fonts32732
-Node: Command prompts33728
-Node: Completion UIs35533
-Node: Org mode blocks38323
-Node: Heading styles40203
-Node: UI typeface44557
-Node: Palette overrides45488
-Node: Advanced customization49877
-Node: Palette override presets51540
-Node: Stylistic variants using palette overrides54414
-Node: Make the mode line borderless56326
-Node: Make the active mode line colorful57928
-Node: Make the tab bar more or less colorful59873
-Node: Make the fringe invisible or another color62104
-Node: Make links use subtle or no underlines63598
-Node: Make prompts more or less colorful64595
-Node: Make completion matches more or less colorful66259
-Node: Make comments yellow and strings green70159
-Node: Make code syntax use the old alt-syntax style72062
-Node: Make use of alternative styles for code syntax75343
-Node: Make matching parenthesis more or less intense79007
-Node: Make box buttons more or less gray80443
-Node: Make TODO and DONE more or less intense81749
-Node: Make headings more or less colorful83452
-Node: Make Org agenda more or less colorful85852
-Node: Make inline code in prose use alternative styles89312
-Node: Make mail citations and headers more or less colorful91853
-Node: Make the region preserve text colors plus other styles94548
-Node: Make mouse highlights more or less colorful96359
-Node: Make language underlines less colorful97666
-Node: Make line numbers use alternative styles99112
-Node: Make diffs use only a foreground101049
-Node: Make deuteranopia diffs red and blue instead of yellow and blue103819
-Node: Make the themes look like what the maintainer uses106241
-Node: More accurate colors in terminal emulators110939
-Node: Range of color with terminal emulators112231
-Node: Preview theme colors114945
-Node: Per-theme customization settings116790
-Node: Get a single color from the palette118136
-Node: Use theme colors in code with modus-themes-with-colors120445
-Node: Do not extend the region background122778
-Node: Add padding to mode line123576
-Node: Remap face with local value126134
-Node: Font configurations for Org and others128557
-Ref: Font configurations for Org and others-Footnote-1131466
-Node: Configure bold and italic faces131653
-Node: Custom Org todo keyword and priority faces135810
-Node: Custom Org emphasis faces139375
-Node: Update Org block delimiter fontification144198
-Node: Measure color contrast146115
-Node: Load theme depending on time of day148813
-Node: Backdrop for pdf-tools149823
-Node: Toggle themes without reloading them152722
-Node: A theme-agnostic hook for theme loading153998
-Node: Use more spacious margins or padding in Emacs frames156451
-Node: Custom hl-todo colors160337
-Node: Add support for solaire-mode161875
-Node: Face coverage164786
-Node: Supported packages165238
-Node: Indirectly covered packages170751
-Node: Notes on individual packages172104
-Node: Note on calendarel weekday and weekend colors173204
-Node: Note on git-gutter in Doom Emacs174352
-Node: Note on php-mode multiline comments176693
-Node: Note on underlines in compilation buffers177446
-Node: Note on inline Latex in Org buffers178283
-Node: Note on dimmerel178893
-Node: Note on display-fill-column-indicator-mode180378
-Node: Note on highlight-parenthesesel181777
-Node: Note on mmm-modeel background colors187755
-Node: Note for prism190055
-Node: Note on company-mode overlay pop-up193223
-Ref: Note on company-mode overlay pop-up-Footnote-1193953
-Ref: Note on company-mode overlay pop-up-Footnote-2194020
-Node: Note on ERC escaped color sequences194075
-Ref: Note on ERC escaped color sequences-Footnote-1195503
-Node: Note on powerline or spaceline195613
-Node: Note on SHR colors196027
-Node: Note on SHR fonts196451
-Node: Note on Ement colors and fonts197090
-Node: Note on pdf-tools link hints198600
-Node: Note on the Notmuch logo201060
-Node: Note on goto-address-mode faces201598
-Node: Frequently Asked Questions202710
-Node: Is the contrast ratio about adjacent colors?203341
-Node: What does it mean to avoid exaggerations?204848
-Node: Why are colors mostly variants of blue magenta cyan?206698
-Node: What is the best setup for legibility?211004
-Node: Are these color schemes?213649
-Node: Port the Modus themes to other platforms?217331
-Node: Contributing220175
-Node: Sources of the themes220572
-Node: Issues you can help with221466
-Node: Patches require copyright assignment to the FSF222857
-Node: Acknowledgements225077
-Node: GNU Free Documentation License229154
-Node: Indices254518
-Node: Function index254697
-Node: Variable index255880
-Node: Concept index258336
+Node: How do the themes look like10901
+Node: Learn about the latest changes11260
+Node: Installation11648
+Node: Install manually from source12578
+Node: Install from the archives13403
+Node: Install on GNU/Linux14002
+Node: Debian 11 Bullseye14495
+Node: GNU Guix14905
+Node: Dealing with byte compilation errors15188
+Node: Enable and load16346
+Node: The require-theme for built-in Emacs themes19200
+Node: Sample configuration with and without use-package20320
+Node: Differences between loading and enabling23231
+Node: Customization options25269
+Node: Custom reload theme29017
+Node: Disable other themes29925
+Node: Bold constructs31105
+Node: Italic constructs31942
+Node: Mixed fonts32713
+Node: Command prompts33709
+Node: Completion UIs35514
+Node: Org mode blocks38304
+Node: Heading styles40184
+Node: UI typeface44538
+Node: Palette overrides45469
+Node: Advanced customization49804
+Node: Palette override presets51467
+Node: Stylistic variants using palette overrides54259
+Node: Make the mode line borderless56171
+Node: Make the active mode line colorful57773
+Node: Make the tab bar more or less colorful59718
+Node: Make the fringe invisible or another color61949
+Node: Make links use subtle or no underlines63443
+Node: Make prompts more or less colorful64440
+Node: Make completion matches more or less colorful66104
+Node: Make comments yellow and strings green70004
+Node: Make code syntax use the old alt-syntax style71907
+Node: Make use of alternative styles for code syntax75188
+Node: Make matching parenthesis more or less intense78852
+Node: Make box buttons more or less gray80288
+Node: Make TODO and DONE more or less intense81594
+Node: Make headings more or less colorful83297
+Node: Make Org agenda more or less colorful85697
+Node: Make inline code in prose use alternative styles89157
+Node: Make mail citations and headers more or less colorful91698
+Node: Make the region preserve text colors plus other styles94393
+Node: Make mouse highlights more or less colorful96204
+Node: Make language underlines less colorful97511
+Node: Make line numbers use alternative styles98957
+Node: Make diffs use only a foreground100894
+Node: Make deuteranopia diffs red and blue instead of yellow and blue103664
+Node: Make the themes look like what the maintainer uses106086
+Node: More accurate colors in terminal emulators110784
+Node: Range of color with terminal emulators112076
+Node: Preview theme colors114790
+Node: Per-theme customization settings116635
+Node: Get a single color from the palette117981
+Node: Use theme colors in code with modus-themes-with-colors120223
+Node: Do not extend the region background122556
+Node: Add padding to mode line123354
+Node: Remap face with local value125912
+Node: Font configurations for Org and others128335
+Ref: Font configurations for Org and others-Footnote-1131244
+Node: Configure bold and italic faces131431
+Node: Custom Org todo keyword and priority faces135588
+Node: Custom Org emphasis faces139153
+Node: Update Org block delimiter fontification143976
+Node: Measure color contrast145893
+Node: Load theme depending on time of day148591
+Node: Backdrop for pdf-tools149601
+Node: Toggle themes without reloading them152500
+Node: A theme-agnostic hook for theme loading153776
+Node: Use more spacious margins or padding in Emacs frames156229
+Node: Custom hl-todo colors160115
+Node: Add support for solaire-mode161653
+Node: Face coverage164564
+Node: Supported packages165016
+Node: Indirectly covered packages170415
+Node: Notes on individual packages171768
+Node: Note on calendarel weekday and weekend colors172868
+Node: Note on git-gutter in Doom Emacs174016
+Node: Note on php-mode multiline comments176357
+Node: Note on underlines in compilation buffers177110
+Node: Note on inline Latex in Org buffers177947
+Node: Note on dimmerel178557
+Node: Note on display-fill-column-indicator-mode180042
+Node: Note on highlight-parenthesesel181441
+Node: Note on mmm-modeel background colors187419
+Node: Note for prism189719
+Node: Note on company-mode overlay pop-up192887
+Ref: Note on company-mode overlay pop-up-Footnote-1193617
+Ref: Note on company-mode overlay pop-up-Footnote-2193684
+Node: Note on ERC escaped color sequences193739
+Ref: Note on ERC escaped color sequences-Footnote-1195167
+Node: Note on powerline or spaceline195277
+Node: Note on SHR colors195691
+Node: Note on SHR fonts196115
+Node: Note on Ement colors and fonts196754
+Node: Note on pdf-tools link hints198264
+Node: Note on the Notmuch logo200724
+Node: Note on goto-address-mode faces201262
+Node: Frequently Asked Questions202374
+Node: Is the contrast ratio about adjacent colors?203005
+Node: What does it mean to avoid exaggerations?204512
+Node: Why are colors mostly variants of blue magenta cyan?206362
+Node: What is the best setup for legibility?210668
+Node: Are these color schemes?213313
+Node: Port the Modus themes to other platforms?216995
+Node: Contributing219839
+Node: Sources of the themes220236
+Node: Issues you can help with221130
+Node: Patches require copyright assignment to the FSF222521
+Node: Acknowledgements224741
+Node: GNU Free Documentation License228818
+Node: Indices254182
+Node: Function index254361
+Node: Variable index255544
+Node: Concept index258000
End Tag Table
diff --git a/doc/modus-themes.org b/doc/modus-themes.org
index 9d7c4382b6..7809bd0391 100644
--- a/doc/modus-themes.org
+++ b/doc/modus-themes.org
@@ -4,9 +4,9 @@
#+language: en
#+options: ':t toc:nil author:t email:t num:t
#+startup: content
-#+macro: stable-version 4.1.0
-#+macro: release-date 2023-02-22
-#+macro: development-version 4.2.0-dev
+#+macro: stable-version 4.2.0
+#+macro: release-date 2023-05-30
+#+macro: development-version 4.3.0-dev
#+macro: file @@texinfo:@file{@@$1@@texinfo:}@@
#+macro: space @@texinfo:@: @@
#+macro: kbd @@texinfo:@kbd{@@$1@@texinfo:}@@
@@ -105,19 +105,19 @@ The Modus themes consist of eight themes, divided into
four subgroups.
~modus-vivendi-tritanopia~ are optimized for users with blue-yellow
color deficiency. The idea is the same as with the deuteranopia
variants: color coding relies only on hues that are accessible to
- people with tritanopia or tritanomaly.
-
-[ The tritanopia themes are part of {{{development-version}}}. ]
+ people with tritanopia or tritanomaly, namely, shades of red and
+ cyan.
To ensure that users have a consistently accessible experience, the
themes strive to achieve as close to full face coverage as possible,
while still targeting a curated list of well-maintained packages
([[#h:a9c8f29d-7f72-4b54-b74b-ddefe15d6a19][Face coverage]]).
-The overarching objective of this project is to always offer accessible
-color combinations. There shall never be a compromise on this
-principle. If there arises an inescapable trade-off between readability
-and stylistic considerations, we will always opt for the former.
+The overarching objective of this project is to always offer
+accessible color combinations. There shall never be a compromise on
+this principle. If there arises an inescapable trade-off between
+usability and stylistic considerations, we will always opt for the
+former.
Starting with version 0.12.0 and onwards, the themes are built into GNU
Emacs.
@@ -1091,8 +1091,6 @@ palette variable is =THEME-NAME-palette-overrides=, thus
yielding:
#+vindex: modus-vivendi-tritanopia-palette-overrides
+ ~modus-vivendi-tritanopia-palette-overrides~
-[ The tritanopia themes are part of {{{development-version}}}. ]
-
Theme-specific overrides take precedence over the shared ones. It is
strongly advised that shared overrides do NOT alter color values, as
those will not be appropriate for both dark and light themes. Common
@@ -1232,9 +1230,6 @@ For some stylistic variation try the "cooler" and
"warmer" presets:
(setq modus-themes-common-palette-overrides
modus-themes-preset-overrides-warmer)
#+end_src
-[ The "warmer" and "cooler" preset overrides are part of
- {{{development-version}}}. ]
-
Note that the user is not limited to those presets. The system of
overrides we provide makes it possible to tweak the value of each
individual named color and to change how values are assigned to
@@ -2740,10 +2735,9 @@ for palette overrides. Else it reads only the default
palette.
[[#h:34c7a691-19bb-4037-8d2f-67a07edab150][Option for palette overrides]].
-With optional =THEME= as a symbol among ~modus-themes-items~, use the
-palette of that item. Else use the current Modus theme. [As part of
-{{{development-version}}}, the ~modus-themes-items~ has an alias
-called ~modus-themes-collection~.]
+With optional =THEME= as a symbol among ~modus-themes-items~ (alias
+~modus-themes-collection~), use the palette of that item. Else use
+the current Modus theme.
If =COLOR= is not present in the palette, this function returns the
~unspecified~ symbol, which is safe when used as a face attribute's
@@ -3893,7 +3887,7 @@ have lots of extensions, so the "full support" may not be
100% true…
+ dired-narrow
+ dired-subtree
+ diredfl
-+ disk-usage [Part of {{{development-version}}}]
++ disk-usage
+ display-fill-column-indicator-mode
+ doom-modeline
+ ediff
@@ -3958,8 +3952,8 @@ have lots of extensions, so the "full support" may not be
100% true…
+ ivy*
+ ivy-posframe
+ jira (org-jira)
-+ jit-spell [Part of {{{development-version}}}]
-+ jinx [Part of {{{development-version}}}]
++ jit-spell
++ jinx
+ journalctl-mode
+ js2-mode
+ julia
@@ -4011,7 +4005,7 @@ have lots of extensions, so the "full support" may not be
100% true…
+ powerline
+ prism ([[#h:a94272e0-99da-4149-9e80-11a7e67a2cf2][Note for prism.el]])
+ prescient
-+ proced [Expanded as part of {{{development-version}}}.]
++ proced
+ prodigy
+ pulse
+ pyim
@@ -4024,7 +4018,7 @@ have lots of extensions, so the "full support" may not be
100% true…
+ rg (rg.el)
+ ripgrep
+ rmail
-+ rst-mode [Part of {{{development-version}}}.]
++ rst-mode
+ ruler-mode
+ sesman
+ shell-script-mode
diff --git a/modus-themes.el b/modus-themes.el
index 815a693739..43c10043bc 100644
--- a/modus-themes.el
+++ b/modus-themes.el
@@ -6,7 +6,7 @@
;; Maintainer: Modus-Themes Development <~protesilaos/modus-the...@lists.sr.ht>
;; URL: https://git.sr.ht/~protesilaos/modus-themes
;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
-;; Version: 4.1.1
+;; Version: 4.2.0
;; Package-Requires: ((emacs "27.1"))
;; Keywords: faces, theme, accessibility
