[elpa] externals/modus-themes a082d7739f: Update to modus-themes version 4.4.0

[ELPA Syncer]

branch: externals/modus-themes
commit a082d7739f627523c6d9098c869cf143fa60b014
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Update to modus-themes version 4.4.0
---
 CHANGELOG.org         | 422 ++++++++++++++++++++++++++++++++++++++++++++++++++
 doc/modus-themes.info | 184 +++++++++++-----------
 doc/modus-themes.org  |  20 +--
 modus-themes.el       |   2 +-
 4 files changed, 519 insertions(+), 109 deletions(-)

diff --git a/CHANGELOG.org b/CHANGELOG.org
index 1eadc99ab7..17b4c7cf22 100644
--- a/CHANGELOG.org
+++ b/CHANGELOG.org
@@ -15,6 +15,428 @@ For further details, please consult these additional 
resources:
 + Manual :: <https://protesilaos.com/emacs/modus-themes>
 + Screenshots :: <https://protesilaos.com/emacs/modus-themes-pictures>
 
+* 4.4.0
+:PROPERTIES:
+:CUSTOM_ID: h:4025f2f4-8524-49d9-9ee5-627361ff9875
+:END:
+
+Before I cover the changes, a brief note about the canonical source of
+the ~modus-themes~ source code and corresponding documentation.
+
+The ~modus-themes~ are built into Emacs, as of version 28, but they
+are not developed in =emacs.git=: I maintain my own Git repository
+(<https://github.com/protesilaos/modus-themes>) and sync with
+=emacs.git= whenever I publish a new version, such as this one. This
+means that my code is often ahead of the one in the Emacs tree
+(including the =master= branch). Similarly, the official manual, which
+is hosted on my website (<https://protesilaos.com/emacs/modus-themes>),
+covers topics not found in the corresponding =gnu.org= web pages.
+
+In the opening section of the manual I include references to the
+canonical sources, but I still get comments about GNU web pages that I
+do not control. Please check those links before reporting issues that
+I can do nothing about.
+
+** No more SourceHut
+:PROPERTIES:
+:CUSTOM_ID: h:56191859-93e5-444a-9356-f393343619a5
+:END:
+
+Development continues on GitHub with GitLab as a mirror. I explained
+my reasons here: 
<https://protesilaos.com/codelog/2024-01-27-sourcehut-no-more/>.
+
+This is a change that affects all my Emacs packages.
+
+** Code blocks now have a background by default
+:PROPERTIES:
+:CUSTOM_ID: h:6b40d5f3-ae0a-4ec5-ab23-20ec64e37773
+:END:
+
+The user option ~modus-themes-org-blocks~ is obsolete. All code blocks
+now have a subtle grey background out-of-the-box. The block delimiter
+lines, such as the =#+begin_src= in Org mode, use the same background
+as the block's contents. This produces a style that (i) is easy to
+notice and (ii) employs minimal colouration. Furthermore, we no longer
+have any discrepancy between Org and similar modes like Markdown.
+
+Every theme has relevant semantic palette mappings to affect the
+underlying faces:
+
+- =bg-prose-block-delimiter=
+- =fg-prose-block-delimiter=
+- =bg-prose-block-contents=
+
+The old =prose-block= is now renamed to =fg-prose-block-delimiter=.
+Please update any such references in your configuration file.
+
+Users can customise those either for all themes via the user option
+~modus-themes-common-palette-overrides~  or on a per-theme basis with
+something like ~modus-operandi-palette-overrides~. The manual includes
+ready-to-use code samples that showcases the numerous permutations made
+possible by these new mappings: 
<https://protesilaos.com/emacs/modus-themes#h:f44cc6e3-b0f1-4a5e-8a90-9e48fa557b50>.
+
+The old option to affect the user option ~org-src-block-faces~ as to
+have a different background for each specified programming language is
+no longer available. The previous design was inflexible, as I was
+hardcoding values for a few languages. Whereas it is better to empower
+the user with the choice of =language->colour= association. The manual
+shows how to do this:
+<https://protesilaos.com/emacs/modus-themes#h:8c842804-43b7-4287-b4e9-8c07d04d1f89>.
+
+** More semantic mappings more inline code in prose-centric modes
+:PROPERTIES:
+:CUSTOM_ID: h:1d6ae039-cc19-479f-b16f-839481f3080a
+:END:
+
+For Org, Markdown, and related we have semantic palette mappings that
+target inline code constructs. For example, in Org we can have text
+inside of tilde signs to mark it up as code. In prior versions, the
+mappings were limited to just a foreground, but now they cover
+background values as well. By default, these background do not have a
+colour associated with them, meaning that the out-of-the-box aesthetic
+is the same as before. Users simply have more power at their disposal
+to tweak the theme to their liking.
+
+Here are the names of those mappings:
+
+- =bg-prose-code=
+- =fg-prose-code=
+- =bg-prose-macro=
+- =fg-prose-macro=
+- =bg-prose-verbatim=
+- =fg-prose-verbatim=
+
+The old =prose-code=, =prose-macro=, and =prose-verbatim= are named
+=fg-prose-code=, =fg-prose-macro=, =fg-prose-verbatim=. Please
+update any such references in your configuration file.
+
+The manual shows lots of examples on how to benefit from these
+optional backgrounds: 
<https://protesilaos.com/emacs/modus-themes#h:bb5b396f-5532-4d52-ab13-149ca24854f1>.
+
+** No colour-coding for =transient.el= buffers.
+:PROPERTIES:
+:CUSTOM_ID: h:0b134a92-9554-4578-a963-ef782f224b28
+:END:
+
+In a recent version of =transient.el=, there is a new user option that
+applies colour-coding to keys (e.g. we see those while using ~magit~):
+~transient-semantic-coloring~. This option is enabled by default,
+changing the previous style that was used as a reference for all my
+designs.
+
+The idea with such colour coding is to indicate when a key continues
+to display the transient, exits with a given action, and the like. For
+our purposes this interface cannot work:
+
+- We need some place to teach users what each colour means, as there
+  are no indicators of any sort to help them (whereas, say, in diff
+  buffers we have the plus and minus signs).
+
+- Not all hues are suitable for highlighting a single character. In
+  light themes, for example, green and yellow colours are awkward
+  choices for the requirements of this interface where the key must be
+  clearly visible. But when we introduce multiple colours, each with
+  their own meaning, we will not be able to avoid those hues.
+
+- The style of key bindings is not limited to =transient.el=. We find
+  them when we invoke =M-x=, do =M-x describe-bindings=, while using
+  the ~which-key~ package, and many more. If we are to change how
+  =transient.el= shows key bindings, then we have to retain the same
+  visual cues for other contexts. Otherwise, everything is inconsistent.
+
+- All themes must use the same colours to preserve the colour coding,
+  thus removing an important aspect of their presentation.
+
+- This whole paradigm does not work for themes that are optimised for
+  users with colour deficiency, due to the reduced number of suitable
+  hues. With deuteranopia, for example, we can only rely on yellow and
+  blue: since yellow is not optimal for single key highlights against
+  a light backdrop, blue is the only hue that works in such a context.
+
+The ~modus-themes~ will never support ~transient-semantic-coloring~.
+All relevant faces use the style of standard key bindings.
+
+Themes can enforce user option values, but I have decided to change
+the faces instead to better communicate my intent. If a user wants
+semantic colouring, they can change the faces to whatever they like.
+
+I understand this is a radical measure, though it is the best I can do
+given the circumstances. If =transient.el= where to have accompanying
+characters that better denote what each key does (e.g. the plus sign
+is for keys that continue the transient), then I am happy to apply
+appropriate colours to those and reconsider the aforementioned.
+
+** Semantic mappings for active arguments and values
+:PROPERTIES:
+:CUSTOM_ID: h:909053eb-0378-41f5-b32a-741fa53ba4a3
+:END:
+
+In various interfaces such as of ~eldoc-mode~ and =transient.el= there
+are highlights for the current argument or argument value. These now
+have corresponding semantic palette mappings and are thus styled
+uniformly (and can be overridden accordingly). The mappings are:
+
+- =bg-active-argument=
+- =fg-active-argument=
+- =bg-active-value=
+- =fg-active-value=
+
+** A semantic mapping for formulas in tables
+:PROPERTIES:
+:CUSTOM_ID: h:306889ed-64c8-414c-a744-14ea1e6b3e6d
+:END:
+
+The =prose-table-formula= applies to inline formula expressions in
+plain text tables. Org mode uses those, as does the minor mode ~orgtbl-mode~.
+The inline formula is meant to stand out from the rest of the table,
+without exaggerations.
+
+** Matching parentheses have semantic mappings for their foreground too
+:PROPERTIES:
+:CUSTOM_ID: h:4055d50e-0153-4576-bba5-fcdcdf039b10
+:END:
+
+By default, Emacs will highlight the matching (opening or closing)
+delimiter when the cursor is next to it. This is useful in Lisp
+programming modes, for example, as we can quickly get a sense of where
+an expression starts and ends.
+
+The themes now provide mappings for the foreground of those
+delimiters. This means that users can either change the combination of
+background and foreground or opt to only display a foreground value
+for a more minimal look.
+
+As always, the manual shows concrete examples:
+<https://protesilaos.com/emacs/modus-themes#h:259cf8f5-48ec-4b13-8a69-5d6387094468>.
+
+** Search highlights have their own semantic mappings
+:PROPERTIES:
+:CUSTOM_ID: h:df3879a4-e11d-47f0-9330-a2d51e999941
+:END:
+
+This makes it easier to differentiate their style on a per-theme
+basis, which I do for all the Modus themes. It also gives users the
+option to override the colours. The mappings:
+
+- =bg-search-current=
+- =bg-search-lazy=
+- =bg-search-replace=
+- =bg-search-rx-group-0=
+- =bg-search-rx-group-1=
+- =bg-search-rx-group-2=
+- =bg-search-rx-group-3=
+
+** Stylistic tweaks to ~modus-operandi-tinted~
+:PROPERTIES:
+:CUSTOM_ID: h:8885de5e-be29-45cc-a2e5-2dcb0866273d
+:END:
+
+The ~modus-operandi-theme~ uses a light ochre background, which gives
+a warmer feel than the pure white background of ~modus-operandi~. To
+better contribute to this warmth, I made some tweaks to common
+elements:
+
+1. The cursor has a red hue as before, but the value is a bit more
+   intense now. This makes it easier to spot in contexts where text is
+   already "warm", like close to an Org =TODO= keyword or in
+   programming mode comments.
+
+2. All key bindings have a red hue instead of blue. We can notice the
+   effect in Help mode buffers that mention where a command is bound,
+   while using ~which-key-mode~, in =transient.el= buffers, in
+   minibuffer completion annotations, and more.
+
+These are in addition to many nuances already built into 
~modus-operandi-tinted~.
+
+I hope that existing users will appreciate these tweaks. We anyway
+have the option to override any entry in the palette, though I suggest
+you give these a chance before enacting any changes.
+
+** Stylistic tweaks to ~modus-vivendi-tinted~
+:PROPERTIES:
+:CUSTOM_ID: h:dc23c419-d87a-4973-9175-961af9e3051d
+:END:
+
+Same principle here as with the above set of changes. Namely:
+
+1. The cursor uses a more intense magenta background to be easier to
+   spot.
+
+2. Key bindings are purple instead of blue to better complement the
+   aesthetics of this theme.
+
+3. The background highlight applied to matching parentheses (per
+   ~show-paren-mode~) is grey-cyan instead of cyan.
+
+Again, we can override everything but please try those for a little
+while.
+
+** The ~olivetti-fringe~ is visible when needed
+:PROPERTIES:
+:CUSTOM_ID: h:3c2d3f21-7686-4376-a3ec-82240b283eec
+:END:
+  
+This is subject to the user option ~olivetty-style~, which can be set
+to the value of =fancy= to produce a page-like effect.
+
+Thanks to Dhavan Vaidya and Gautier Ponsinet for bringing this matter
+to my attention on the now-discontinued mailing list:
+<https://lists.sr.ht/~protesilaos/modus-themes/%3Cm2a5qzpi3y.fsf%40muon.local.mail-host-address-is-not-set%3E>
+
+** A more subtle style for the ~consult-preview-insertion~ face
+:PROPERTIES:
+:CUSTOM_ID: h:8c6717d2-0488-4590-8083-52e081adf6f5
+:END:
+  
+The default value of that face inherits from the ~region~ face. This
+is fine in some cases, though not when the user calls
+~consult-outline~ in a buffer with hidden text (e.g. Org folded
+headings). There the background is applied to the entire heading's
+surface area, which is too distracting while cycling through
+completion candidates and inspecting the preview.
+
+** Simpler ~imenu-list~ with four colours
+:PROPERTIES:
+:CUSTOM_ID: h:af7ec9f7-e7aa-4a05-a5a2-184d0d7143c6
+:END:
+
+The ~imenu-list~ defines two sets of faces which apply to same heading
+levels but differ on whether the heading has subheadings or not.
+Before, we would colourise those differently, which could be
+confusing. Now they look the same, which is fine because the interface
+has additional markup to show when subheadings are present.
+  
+Thanks to ltmsyvag for pointing this out in issue 95:
+<https://github.com/protesilaos/modus-themes/issues/95>.
+
+** Implicit buttons in Gnus are no longer underlined
+:PROPERTIES:
+:CUSTOM_ID: h:6b0cc04f-1a9b-436c-b11f-5446ea55b010
+:END:
+
+Gnus buttonises text that it considers actionable. The exact
+functionality depends on the context, but it basically does stuff like
+add a quick way to write a new message to a given email address. These
+buttons can be mistaken for links, so I am removing their underline to
+avoid any possible confusion.
+
+** The ~message-separator~ face is less intense
+:PROPERTIES:
+:CUSTOM_ID: h:a049f538-2805-4379-8542-43dc6f990a2b
+:END:
+
+In message/email composition buffers, there is a line that
+distinguishes headers from the body of the message. By default, it
+reads =--text follows this line--= and will now have a subtle grey
+background. The idea is to not stress the distinction between headers
+and body, as this line's verbosity is already enough to call attention
+to it when we add a subtle background.
+
+** Recalibrated all "nuanced" background values
+:PROPERTIES:
+:CUSTOM_ID: h:ecb9c704-7615-4e42-8438-13e96c10588e
+:END:
+
+Each theme has a subset of slightly accented background named
+=bg-{red,green,blue,yellow,magenta,cyan}-nuanced=. These have slightly
+different values to be more consistent in terms of their intensity.
+
+** The ~debbugs~ package is now supported
+:PROPERTIES:
+:CUSTOM_ID: h:67161fd3-f615-4856-b5df-99f5c0f2e5ee
+:END:
+
+Thanks to Gautier Ponsinet for sending me the relevant patch to my
+personal email. I made further stylistic changes on top.
+
+** The ~ztree~ package is covered as well
+:PROPERTIES:
+:CUSTOM_ID: h:c82277b9-abb9-4d1e-9912-14caf66af8d2
+:END:
+
+It produces a diff between two directories and thus needs appropriate
+colours.
+
+** Added support for ~xterm-color~ and ~rustic-mode~
+:PROPERTIES:
+:CUSTOM_ID: h:c262fdbe-49a5-480b-b0d1-6592f6e29879
+:END:
+
+These are basically reusing styles we already support for other
+terminal emulators. Thanks to Tony Zorman for the contribution, which
+was done in pull request 99: 
<https://github.com/protesilaos/modus-themes/pull/99>.
+
+** Org checkboxes are monospaced when ~modus-themes-mixed-fonts~ is non-nil
+:PROPERTIES:
+:CUSTOM_ID: h:69dbe924-58b3-43e9-801c-35cf9ac8fffb
+:END:
+
+The user option ~modus-themes-mixed-fonts~ makes specing-sensitive
+elements use a monospaced font (specifically, the font family of the
+~fixed-pitch~ face). This lets the user set a more prose-friendly
+style without visually breaking snippets that rely on fixed width
+spacing. A prose-friendly style is done by making the default font a
+proportionately spaced one, or by enabling ~variable-pitch-mode~ in
+the current buffer.
+
+For this case, we now cover Org checkboxes as well to avoid
+misalignments in checklists.
+
+Thanks to Gautier Ponsinet for discussing this with me via email and
+sending the relevant patch.
+
+** More code samples in the manual
+:PROPERTIES:
+:CUSTOM_ID: h:2ccb1b44-a36e-4ea1-9f24-9d080cdec02d
+:END:
+
+The manual documents everything about the customisation options
+provided by the themes, as well as relevant do-it-yourself code
+samples. I now include more examples and better explain how to hook
+those either to the ~enable-theme-functions~ or the
+~modus-themes-after-load-theme-hook~. If something is not clear or not
+covered at all, please let me know and I will help you do what you
+want.
+
+** Miscellaneous
+:PROPERTIES:
+:CUSTOM_ID: h:2e5f0804-236d-49b5-9b2f-ecb4794b244b
+:END:
+
+- All =cl-= snippets are removed from the source code. We did not
+  really need them and I rewrote the code accordingly. This is not a
+  value judgement against Common Lisp patterns in Emacs Lisp (I do not
+  mind them): it is just a matter of removing a dependency for things
+  that can easily be done differently.
+
+- The ~keycast-key~ inherits the ~bold~ face if the user option
+  ~modus-themes-bold-constructs~ is set to a non-nil value.
+
+- The ~read-multiple-choice-face~ now has a cooler hue than the one it
+  had before. This way it is not mistaken for a warning.
+
+- The ~appt-notification~ face uses a foreground value that is better
+  suited for the modeline, where this indicator appears.
+
+- The ~header-line-highlight~ draws a box around it. This makes the
+  mouse hover effect easier to spot.
+
+- The ~shr-mark~ face is now covered as well. It uses an appropriate
+  background colour.
+
+- The ~mct-highlight-candidate~ face is covered and has an appropriate
+  style for the minibuffer completions.
+
+- The ~completions-highlight~ face (Emacs 29) is also supported to
+  ensure stylistic consistency between the minibuffer interfaces
+  covered by the themes.
+
+- Flagged and deleted messages in ~mu4e~ and ~notmuch~ use different
+  hues to not conflate the two.
+
+- Fixed the spelling of "colour" to "color" in the manual because core
+  Emacs uses the latter...
+
 * 4.3.0
 :PROPERTIES:
 :CUSTOM_ID: h:4783bc29-3055-426d-9acb-51e4d0741871
diff --git a/doc/modus-themes.info b/doc/modus-themes.info
index 72780fefbf..79ef6dbba4 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.3.0, released on 2023-09-19.  Any reference to a newer feature which
+4.4.0, released on 2024-03-17.  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.4.0-dev.
+   Current development target is 4.5.0-dev.
 
    • Package name (GNU ELPA): ‘modus-themes’
    • Official manual: <https://protesilaos.com/emacs/modus-themes>
@@ -2146,8 +2146,6 @@ show how to change the background of matching delimiters 
when
 ‘show-paren-mode’ is enabled.  We also demonstrate how to enable
 underlines for those highlights.
 
-   [ The ‘fg-paren-match’ is part of 4.4.0-dev.  ]
-
      ;; Change the background to a shade of magenta
      (setq modus-themes-common-palette-overrides
            '((bg-paren-match bg-magenta-intense)))
@@ -2277,11 +2275,9 @@ File: modus-themes.info,  Node: DIY Make Org block 
colors more or less colorful,
 7.2.15 DIY Make Org block colors more or less colorful
 ------------------------------------------------------
 
-[ Expanded as part of 4.4.0-dev.  ]
-
-   This is one of our practical examples to override the semantic colors
-of the Modus themes (*note Stylistic variants using palette overrides:
-DIY Stylistic variants using palette overrides.).  Here we show how to
+This is one of our practical examples to override the semantic colors of
+the Modus themes (*note Stylistic variants using palette overrides: DIY
+Stylistic variants using palette overrides.).  Here we show how to
 change the presentation of Org blocks (and other such blocks like
 Markdown fenced code sections, though the exact presentation depends on
 each major mode).
@@ -2444,11 +2440,9 @@ File: modus-themes.info,  Node: DIY Make inline code in 
prose use alternative st
 7.2.17 DIY Make inline code in prose use alternative styles
 -----------------------------------------------------------
 
-[ Expanded as part of 4.4.0-dev.  ]
-
-   This is one of our practical examples to override the semantic colors
-of the Modus themes (*note Stylistic variants using palette overrides:
-DIY Stylistic variants using palette overrides.).  In the following code
+This is one of our practical examples to override the semantic colors of
+the Modus themes (*note Stylistic variants using palette overrides: DIY
+Stylistic variants using palette overrides.).  In the following code
 block we show how to affect constructs such as Org’s verbatim, code, and
 macro entries.  We also provide mappings for tables, property drawers,
 tags, and code block delimiters, though we do not show every possible
@@ -4085,9 +4079,9 @@ have lots of extensions, so the “full support” may not be 
100% true…
    • custom (what you get with ‘M-x customize’)
    • dashboard
    • deadgrep
-   • debbugs [ Part of 4.4.0-dev.  ]
+   • debbugs
    • deft
-   • denote [ Part of 4.4.0-dev.  ]
+   • denote
    • devdocs
    • dictionary
    • diff-hl
@@ -4184,7 +4178,7 @@ have lots of extensions, so the “full support” may not be 
100% true…
    • marginalia
    • markdown-mode
    • markup-faces (‘adoc-mode’)
-   • mct [ Part of 4.4.0-dev.  ]
+   • mct
    • messages
    • minimap
    • mode-line
@@ -4296,7 +4290,7 @@ have lots of extensions, so the “full support” may not be 
100% true…
    • xterm-color (and ansi-colors)
    • yaml-mode
    • yasnippet
-   • ztree [ Part of 4.4.0-dev.  ]
+   • ztree
 
    Plus many other miscellaneous faces that are provided by Emacs.
 
@@ -6329,83 +6323,83 @@ Node: DIY Make comments yellow and strings green77847
 Node: DIY Make code syntax use the old alt-syntax style79556
 Node: DIY Make use of alternative styles for code syntax82679
 Node: DIY Make matching parenthesis more or less intense86141
-Node: DIY Make box buttons more or less gray87569
-Node: DIY Make TODO and DONE more or less intense88582
-Node: DIY Make headings more or less colorful90083
-Node: DIY Make Org block colors more or less colorful92200
-Node: DIY Make Org agenda more or less colorful96614
-Node: DIY Make inline code in prose use alternative styles99789
-Node: DIY Make mail citations and headers more or less colorful102071
-Node: DIY Make the region preserve text colors plus other styles104471
-Node: DIY Make mouse highlights more or less colorful106027
-Node: DIY Make language underlines less colorful107040
-Node: DIY Make line numbers use alternative styles108192
-Node: DIY Make diffs use only a foreground109835
-Node: DIY Make deuteranopia diffs red and blue instead of yellow and 
blue112726
-Node: DIY More accurate colors in terminal emulators115206
-Node: DIY Range of color with terminal emulators116518
-Node: DIY Per-theme customization settings119311
-Node: DIY Do not extend the region background120744
-Node: DIY Add padding to the mode line121548
-Node: DIY Remap face with local value124481
-Node: DIY Font configurations for Org and others127029
-Ref: DIY Font configurations for Org and others-Footnote-1130012
-Node: DIY Configure bold and italic faces130199
-Node: DIY Custom Org todo keyword and priority faces134821
-Node: DIY Custom Org emphasis faces138564
-Node: DIY Use colored Org source blocks per language143445
-Node: DIY Measure color contrast148085
-Node: DIY Load theme depending on time of day150805
-Node: DIY Backdrop for pdf-tools151835
-Node: DIY Toggle themes without reloading them155004
-Node: DIY Use more spacious margins or padding in Emacs frames156313
-Node: DIY Custom hl-todo colors160570
-Node: DIY Add support for solaire-mode162387
-Node: DIY Use a hook at the post-load-theme phase165513
-Node: DIY A theme-agnostic hook for theme loading167637
-Node: Face coverage170268
-Node: Supported packages170720
-Node: Indirectly covered packages176430
-Node: Notes on individual packages177799
-Node: Note on calendarel weekday and weekend colors178899
-Node: Note on git-gutter in Doom Emacs180047
-Node: Note on php-mode multiline comments182547
-Node: Note on underlines in compilation buffers183307
-Node: Note on inline Latex in Org buffers184179
-Node: Note on dimmerel184789
-Node: Note on display-fill-column-indicator-mode186274
-Node: Note on highlight-parenthesesel187727
-Node: Note on mmm-modeel background colors193810
-Node: Note for prism196164
-Node: Note on company-mode overlay pop-up199386
-Ref: Note on company-mode overlay pop-up-Footnote-1200116
-Ref: Note on company-mode overlay pop-up-Footnote-2200183
-Node: Note on ERC escaped color sequences200238
-Ref: Note on ERC escaped color sequences-Footnote-1201666
-Node: Note on powerline or spaceline201776
-Node: Note on SHR colors202190
-Node: Note on SHR fonts202614
-Node: Note on Ement colors and fonts203301
-Node: Note on pdf-tools link hints204811
-Node: Note on the Notmuch logo207271
-Node: Note on goto-address-mode faces207809
-Node: Frequently Asked Questions208927
-Node: Is the contrast ratio about adjacent colors?209560
-Node: What does it mean to avoid exaggerations?211069
-Node: Why are colors mostly variants of blue magenta cyan?212921
-Node: What is the best setup for legibility?217255
-Node: Are these color schemes?219902
-Node: Port the Modus themes to other platforms?223586
-Node: Contributing226432
-Node: Sources of the themes226831
-Node: Issues you can help with227727
-Node: Patches require copyright assignment to the FSF229120
-Node: Acknowledgements231342
-Node: GNU Free Documentation License235512
-Node: Indices260876
-Node: Function index261055
-Node: Variable index262353
-Node: Concept index265047
+Node: DIY Make box buttons more or less gray87513
+Node: DIY Make TODO and DONE more or less intense88526
+Node: DIY Make headings more or less colorful90027
+Node: DIY Make Org block colors more or less colorful92144
+Node: DIY Make Org agenda more or less colorful96518
+Node: DIY Make inline code in prose use alternative styles99693
+Node: DIY Make mail citations and headers more or less colorful101935
+Node: DIY Make the region preserve text colors plus other styles104335
+Node: DIY Make mouse highlights more or less colorful105891
+Node: DIY Make language underlines less colorful106904
+Node: DIY Make line numbers use alternative styles108056
+Node: DIY Make diffs use only a foreground109699
+Node: DIY Make deuteranopia diffs red and blue instead of yellow and 
blue112590
+Node: DIY More accurate colors in terminal emulators115070
+Node: DIY Range of color with terminal emulators116382
+Node: DIY Per-theme customization settings119175
+Node: DIY Do not extend the region background120608
+Node: DIY Add padding to the mode line121412
+Node: DIY Remap face with local value124345
+Node: DIY Font configurations for Org and others126893
+Ref: DIY Font configurations for Org and others-Footnote-1129876
+Node: DIY Configure bold and italic faces130063
+Node: DIY Custom Org todo keyword and priority faces134685
+Node: DIY Custom Org emphasis faces138428
+Node: DIY Use colored Org source blocks per language143309
+Node: DIY Measure color contrast147949
+Node: DIY Load theme depending on time of day150669
+Node: DIY Backdrop for pdf-tools151699
+Node: DIY Toggle themes without reloading them154868
+Node: DIY Use more spacious margins or padding in Emacs frames156177
+Node: DIY Custom hl-todo colors160434
+Node: DIY Add support for solaire-mode162251
+Node: DIY Use a hook at the post-load-theme phase165377
+Node: DIY A theme-agnostic hook for theme loading167501
+Node: Face coverage170132
+Node: Supported packages170584
+Node: Indirectly covered packages176198
+Node: Notes on individual packages177567
+Node: Note on calendarel weekday and weekend colors178667
+Node: Note on git-gutter in Doom Emacs179815
+Node: Note on php-mode multiline comments182315
+Node: Note on underlines in compilation buffers183075
+Node: Note on inline Latex in Org buffers183947
+Node: Note on dimmerel184557
+Node: Note on display-fill-column-indicator-mode186042
+Node: Note on highlight-parenthesesel187495
+Node: Note on mmm-modeel background colors193578
+Node: Note for prism195932
+Node: Note on company-mode overlay pop-up199154
+Ref: Note on company-mode overlay pop-up-Footnote-1199884
+Ref: Note on company-mode overlay pop-up-Footnote-2199951
+Node: Note on ERC escaped color sequences200006
+Ref: Note on ERC escaped color sequences-Footnote-1201434
+Node: Note on powerline or spaceline201544
+Node: Note on SHR colors201958
+Node: Note on SHR fonts202382
+Node: Note on Ement colors and fonts203069
+Node: Note on pdf-tools link hints204579
+Node: Note on the Notmuch logo207039
+Node: Note on goto-address-mode faces207577
+Node: Frequently Asked Questions208695
+Node: Is the contrast ratio about adjacent colors?209328
+Node: What does it mean to avoid exaggerations?210837
+Node: Why are colors mostly variants of blue magenta cyan?212689
+Node: What is the best setup for legibility?217023
+Node: Are these color schemes?219670
+Node: Port the Modus themes to other platforms?223354
+Node: Contributing226200
+Node: Sources of the themes226599
+Node: Issues you can help with227495
+Node: Patches require copyright assignment to the FSF228888
+Node: Acknowledgements231110
+Node: GNU Free Documentation License235280
+Node: Indices260644
+Node: Function index260823
+Node: Variable index262121
+Node: Concept index264815
 
 End Tag Table
 
diff --git a/doc/modus-themes.org b/doc/modus-themes.org
index 68a55add00..2d79594b68 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.3.0
-#+macro: release-date 2023-09-19
-#+macro: development-version 4.4.0-dev
+#+macro: stable-version 4.4.0
+#+macro: release-date 2024-03-17
+#+macro: development-version 4.5.0-dev
 #+macro: file @@texinfo:@file{@@$1@@texinfo:}@@
 #+macro: space @@texinfo:@: @@
 #+macro: kbd @@texinfo:@kbd{@@$1@@texinfo:}@@
@@ -1945,8 +1945,6 @@ this code block we show how to change the background of 
matching
 delimiters when ~show-paren-mode~ is enabled.  We also demonstrate how
 to enable underlines for those highlights.
 
-[ The =fg-paren-match= is part of {{{development-version}}}. ]
-
 #+begin_src emacs-lisp
 ;; Change the background to a shade of magenta
 (setq modus-themes-common-palette-overrides
@@ -2077,8 +2075,6 @@ Reload the theme for changes to take effect.
 :custom_id: h:f44cc6e3-b0f1-4a5e-8a90-9e48fa557b50
 :end:
 
-[ Expanded as part of {{{development-version}}}. ]
-
 This is one of our practical examples to override the semantic colors
 of the Modus themes ([[#h:df1199d8-eaba-47db-805d-6b568a577bf3][Stylistic 
variants using palette overrides]]). Here
 we show how to change the presentation of Org blocks (and other such
@@ -2254,8 +2250,6 @@ Reload the theme for changes to take effect.
 :CUSTOM_ID: h:bb5b396f-5532-4d52-ab13-149ca24854f1
 :END:
 
-[ Expanded as part of {{{development-version}}}. ]
-
 This is one of our practical examples to override the semantic colors
 of the Modus themes ([[#h:df1199d8-eaba-47db-805d-6b568a577bf3][Stylistic 
variants using palette overrides]]).  In
 the following code block we show how to affect constructs such as
@@ -3928,9 +3922,9 @@ have lots of extensions, so the "full support" may not be 
100% true…
 + custom (what you get with {{{kbd(M-x customize)}}})
 + dashboard
 + deadgrep
-+ debbugs [ Part of {{{development-version}}}. ]
++ debbugs
 + deft
-+ denote [ Part of {{{development-version}}}. ]
++ denote
 + devdocs
 + dictionary
 + diff-hl
@@ -4026,7 +4020,7 @@ have lots of extensions, so the "full support" may not be 
100% true…
 + marginalia
 + markdown-mode
 + markup-faces (~adoc-mode~)
-+ mct [ Part of {{{development-version}}}. ]
++ mct
 + messages
 + minimap
 + mode-line
@@ -4138,7 +4132,7 @@ have lots of extensions, so the "full support" may not be 
100% true…
 + xterm-color (and ansi-colors)
 + yaml-mode
 + yasnippet
-+ ztree [ Part of {{{development-version}}}. ]
++ ztree
 
 Plus many other miscellaneous faces that are provided by Emacs.
 
diff --git a/modus-themes.el b/modus-themes.el
index 829f723ede..b776f12671 100644
--- a/modus-themes.el
+++ b/modus-themes.el
@@ -5,7 +5,7 @@
 ;; Author: Protesilaos Stavrou <info@protesilaos.com>
 ;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
 ;; URL: https://github.com/protesilaos/modus-themes
-;; Version: 4.3.0
+;; Version: 4.4.0
 ;; Package-Requires: ((emacs "27.1"))
 ;; Keywords: faces, theme, accessibility