[elpa] externals/modus-operandi-theme e8aeccb 026/153: Remove README.org

[Stefan Monnier]

branch: externals/modus-operandi-theme
commit e8aeccb65f784fd3f498d31cd17ce66ac806282d
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Remove README.org
    
    Superseded by the markdown version which was added in commit e59648753.
---
 README.org | 1522 ------------------------------------------------------------
 1 file changed, 1522 deletions(-)

diff --git a/README.org b/README.org
deleted file mode 100644
index 03eb6f8..0000000
--- a/README.org
+++ /dev/null
@@ -1,1522 +0,0 @@
-#+TITLE: Modus Themes for GNU Emacs
-#+AUTHOR: Protesilaos Stavrou
-#+EMAIL: info@protesilaos.com
-#+OPTIONS: toc:nil
-
-+ README HTML version on my website :: 
[[https://protesilaos.com/modus-themes][https://protesilaos.com/modus-themes]]
-+ Git repo :: 
[[https://gitlab.com/protesilaos/modus-themes/][https://gitlab.com/protesilaos/modus-themes/]]
-
------
-
-#+TOC: headlines 8 insert TOC here, with eight headline levels
-
-* Overview
-:PROPERTIES:
-:CUSTOM_ID: h:d42d56a4-9252-4858-ac8e-3306cdd24e19
-:END:
-
-This is a set of accessible themes for GNU Emacs.  The contrast ratio
-between foreground and background values should always be >= 7:1, which
-conforms with the WCAG AAA accessibility standard.  This is the highest
-standard of its kind.
-
-The /Modus themes/ project consists of two standalone items, one where
-dark text is cast on a light backdrop (Modus Operandi) and another where
-light text is displayed against a dark background (Modus Vivendi).
-
-The themes are *highly customisable* and can be made to look much
-different than their default austere aesthetic.  Make sure to read the
-section on the [[#h:d414ca47-6dce-4905-9f2e-de1465bf23bb][customisation 
options]].
-
-** Links with demo content
-:PROPERTIES:
-:CUSTOM_ID: h:3b1b8ad9-f08f-4329-b9ee-d817b610708f
-:END:
-
-Check the 
[[https://gitlab.com/protesilaos/modus-themes/wikis/Screenshots][Wiki page with 
the screen shots]].  There are lots of scenaria
-on display that draw attention to details and important aspects in the
-design of the themes.  They also showcase the numerous customisation
-options.
-
-Also note that I use these themes in [[https://protesilaos.com/code-casts][my 
Emacs-related screen casts]]
-(although older videos contain earlier, "alpha" versions).
-
-* Install and auto-load
-:PROPERTIES:
-:CUSTOM_ID: h:25c3ecd3-8025-414c-9b96-e4d6266c6fe8
-:END:
-
-** Install the packages
-:PROPERTIES:
-:CUSTOM_ID: h:c3e293e8-8464-4196-aefd-184027116ded
-:END:
-
-If you are tracking Emacs directly from its =master= branch, you do not
-need to install any package as the themes are already built in (starting
-with commit =c1b0515=---for the specifics refer to the section with the
-[[#h:064dc3f2-ef1f-448e-bb11-0efb37884ebe][note about the themes that are 
built into Emacs]]).  Otherwise you are
-running a stable version of Emacs, in which case you should continue
-reading this section.
-
-I maintain /Modus Operandi/ (light theme) and /Modus Vivendi/ (dark) as
-standalone packages in Emacs-specific archives: GNU ELPA, MELPA, and
-MELPA Stable.  There also exist 
[[#h:f696763b-5db1-4717-a90a-964e127d1a73][GNU/Linux distro packages]].
-
-For an interactive method, just run:
-
-#+begin_src
-M-x package-install RET modus-operandi-theme RET
-#+end_src
-
-And/or:
-
-#+begin_src
-M-x package-install RET modus-vivendi-theme RET
-#+end_src
-
-To be clear, that sequence means:
-
-+ press `Meta-X'
-+ type `package-install'
-+ hit the Return key
-+ type the name of the package
-+ hit Return to confirm your choice
-
-*Remember to refresh your package lists* (=M-x package-refresh-contents= or
-=M-x list-packages=), in case Emacs complains that a package is no longer
-available.
-
-*** With the "use-package" configuration manager
-:PROPERTIES:
-:CUSTOM_ID: h:3ab0ac39-38fb-405b-8a15-771cbd843b6d
-:END:
-
-For a declarative approach with =use-package= and the built-in =package.el=,
-you can write something like this (also see 
[[#h:d414ca47-6dce-4905-9f2e-de1465bf23bb][the customisation options]]
-for how to expand these package declarations):
-
-#+BEGIN_SRC emacs-lisp
-(use-package modus-operandi-theme :ensure)
-
-(use-package modus-vivendi-theme :ensure)
-#+END_SRC
-
-*** GNU/Linux distro packages
-:PROPERTIES:
-:CUSTOM_ID: h:f696763b-5db1-4717-a90a-964e127d1a73
-:END:
-
-The themes are also available from the archives of some GNU/Linux
-distributions.  These should correspond to a tagged release rather than
-building directly from the latest Git commit.  It all depends on the
-distro's packaging policies.
-
-/Note for package maintainers:/ Feel free to 
[[https://protesilaos.com/contact/][contact me]] for any questions
-you may have and/or to update this section.
-
-**** Debian ("Sid" or "Unstable")
-:PROPERTIES:
-:CUSTOM_ID: h:a3d891ff-3dc3-4455-a482-b251e59bb21a
-:END:
-
-The two themes are distributed as 
[[https://packages.debian.org/sid/elpa-modus-themes][a single package for 
Debian]] and its
-derivatives.  Currently in the unstable suite and should be available in
-time for Debian 11 "Bullseye" (next stable).
-
-Get them with:
-
-#+begin_src sh
-sudo apt install elpa-modus-themes
-#+end_src
-
-Special thanks to package maintainer Dhavan Vaidya and the rest of the
-Debian Emacsen team!
-
-**** GNU Guix
-:PROPERTIES:
-:CUSTOM_ID: h:fea43d19-b307-46d7-81ab-d0e77e9cbede
-:END:
-
-Users of either GuixSD (the distro) or just Guix (the package manager)
-can get each theme as a standalone package.
-
-#+begin_src sh
-guix package -i modus-operandi-theme
-#+end_src
-
-And/or:
-
-#+begin_src sh
-guix package -i modus-vivendi-theme
-#+end_src
-
-I do not know who the package maintainer is, but I wish to thank you
-regardless!
-
-*** Manual installation method
-:PROPERTIES:
-:CUSTOM_ID: h:0317c29a-3ddb-4a0a-8ffd-16c781733ea2
-:END:
-
-Download the files in this repository ending in =*-theme.el= and place
-them in an appropriate directory, such as =~/.emacs.d/themes/=.  To make
-sure the filesystem path of your choice is read by Emacs, insert the
-following in your initialisation file:
-
-#+BEGIN_SRC emacs-lisp
-(add-to-list 'custom-theme-load-path "~/.emacs.d/themes/")
-#+END_SRC
-
-** Load automatically
-:PROPERTIES:
-:CUSTOM_ID: h:ae978e05-526f-4509-a007-44a0925b8bce
-:END:
-
-To load the theme from your Emacs initialisation file use the relevant
-snippet:
-
-#+BEGIN_SRC emacs-lisp
-(load-theme 'modus-operandi t)          ; Light theme
-(load-theme 'modus-vivendi t)           ; Dark theme
-#+END_SRC
-
-Make sure to /remove any other theme/ that is being loaded, otherwise you
-might run into unexpected issues (you can also =M-x disable-theme=).
-
-*** Load at a given time or at sunset/sunrise
-:PROPERTIES:
-:CUSTOM_ID: h:4e936e31-e9eb-4b50-8fdd-45d827a03cca
-:END:
-
-This is a neat trick contributed by 
[[https://www.reddit.com/r/emacs/comments/gdtqov/weekly_tipstricketc_thread/fq9186h/][b3n
 on r/emacs]].  It will select the
-appropriate theme based on the time of the day and it will also switch
-themes when the time comes.
-
-#+begin_src emacs-lisp
-;; Light for the day
-(load-theme 'modus-operandi t t)
-(run-at-time "05:00" (* 60 60 24)
-             (lambda () (enable-theme 'modus-operandi)))
-
-;; Dark for the night
-(load-theme 'modus-vivendi t t)
-(run-at-time "21:00" (* 60 60 24)
-             (lambda () (enable-theme 'modus-vivendi)))
-#+end_src
-
-A modified version of the above technique was contributed by 
[[https://gitlab.com/aadcg][André
-Alexandre Gomes]].  If you set =calendar-latitude= and =calendar-longitude=
-(defined in the built-in =solar.el= library) in your =init.el=, you can
-automatically switch between both themes at sunrise and sunset.  Note
-that /those calendar variables need to be set before loading the themes/.
-
-#+begin_src emacs-lisp
-;; Light at sunrise
-(load-theme 'modus-operandi t t)
-(run-at-time (nth 1 (split-string (sunrise-sunset)))
-             (* 60 60 24)
-             (lambda () (enable-theme 'modus-operandi)))
-
-;; Dark at sunset
-(load-theme 'modus-vivendi t t)
-(run-at-time (nth 4 (split-string (sunrise-sunset)))
-             (* 60 60 24)
-             (lambda () (enable-theme 'modus-vivendi)))
-#+end_src
-
-For the sake of completeness, the =load-theme= call in these snippets is
-slightly different than the one in the section right above, because it
-does not enable the theme directly: the subsequent =enable-theme= does
-that when needed.
-
-* Customisation options
-:PROPERTIES:
-:CUSTOM_ID: h:d414ca47-6dce-4905-9f2e-de1465bf23bb
-:END:
-
-Both of the Modus themes expose variables that allow users to tweak how
-certain styles are configured.  Check the 
[[https://gitlab.com/protesilaos/modus-themes/wikis/Screenshots][Wiki with the 
screen shots]] to
-see how these will change things.
-
-By default, all variables are deactivated (=nil=), meaning that *you need
-to explicitly opt in* like this:
-
-#+begin_src emacs-lisp
-(setq CUSTOMISATION-OPTION-NAME t)
-
-;; example with "rainbow" headings for Modus Operandi:
-(setq modus-operandi-theme-rainbow-headings t)
-#+end_src
-
-Put the point (cursor) exactly to the right of the closing parenthesis
-and use =C-x C-e= to evaluate each =setq= form individually, or the entire
-expression that holds it (e.g. a function or =use-package= declaration).
-
-All customisation *options must be declared before loading the theme*,
-else they will not be parsed and have no immediate effect.  To [re-]load
-a theme, you can evaluate either of these:
-
-#+begin_src emacs-lisp
-(load-theme 'modus-operandi t)
-(load-theme 'modus-vivendi t)
-#+end_src
-
-Consult the section below with the 
[[#h:0e3b8a62-8d72-4439-be2d-cb12ed98f4cb][complete example configuration]] for 
a
-fully fledged =use-package= declaration.
-
-** Option for "greyscale" or "rainbow" Org blocks
-:PROPERTIES:
-:CUSTOM_ID: h:ca57a3af-6f79-4530-88c0-e35eda9d3bf7
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-org-blocks=
-+ =modus-vivendi-theme-org-blocks=
-
-Possible values:
-
-1. =nil= (default)
-2. =greyscale=
-3. =rainbow=
-
-=greyscale= will apply a subtle neutral grey background to the block's
-contents.  It will also extend to the edge of the window the background
-of the "begin" and "end" block delimiter lines (only relevant for Emacs
-versions >= 27 where the ':extend' keyword is recognised by
-=set-face-attribute=).
-
-=rainbow= will instead use an accented background for the contents of the
-block.  The exact colour will depend on the programming language and is
-controlled by the =org-src-block-faces= variable (refer to the theme's
-source code for the current association list).  This is most suitable
-for users who work on literate programming documents that mix and match
-several languages.
-
-The default is to use the same background as the rest of the buffer for
-the contents of the block.
-
-Note that the "rainbow" blocks may require you to also reload the
-major-mode so that the colours are applied properly: =M-x org-mode= to
-refresh the buffer.  Or start typing in each code block.
-
-** Option for colourful "rainbow" headings
-:PROPERTIES:
-:CUSTOM_ID: h:1be42afb-bcd2-4425-b956-0ba93eb960c2
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-rainbow-headings=
-+ =modus-vivendi-theme-rainbow-headings=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Apply more saturated colours to headings in =org-mode= and =outline-mode=
-while retaining all other heading properties (such as a bold weight and
-the optional scaled height ---see relevant customisation toggle).  The
-colours follow the rainbow's spectrum.  In Org headings, some additional
-tweaks are made to adapt keywords (like "TODO") to the more vivid
-presentation.
-
-The default uses a more frugal aesthetic for headings, letting their
-bold typography and the nuances between the various heading levels
-provide the elements of differentiation.
-
-** Option for sectioned headings
-:PROPERTIES:
-:CUSTOM_ID: h:c1c9a380-7a05-4c0d-b714-2acac88f10ad
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-section-headings=
-+ =modus-vivendi-theme-section-headings=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Uses a background colour and an overline to mark section headings in
-=org-mode= and =outline-mode=.  These attributes are applied in addition to
-the existing foreground colour and the bold weight and can, therefore,
-be combined with the "rainbow" headings option (as well as all the other
-options pertaining to headings).  For Org several additional faces are
-configured accordingly, such as TODO keywords which gain a box style.
-
-The default is to use only a subtle foreground and a bold weight for
-headings, while no boxes or {under,over}-line effects are present.
-
-Note that the background for sectioned headings will extend to the edge
-of the window.  To make it cover just the area occupied by the heading's
-text, use this:
-
-#+begin_src emacs-lisp
-(setq org-fontify-whole-heading-line nil)
-#+end_src
-
-** Option for scaled headings
-:PROPERTIES:
-:CUSTOM_ID: h:db0275ea-11c2-47c9-82a9-10b65d8df0f8
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-scale-headings=
-+ =modus-vivendi-theme-scale-headings=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Make headings larger in size relative to the main text.  This is
-noticeable in modes like Org.  The default is to use the same size for
-headers and body copy.
-
-In addition to toggles for enabling scaled headings, users can also
-specify a number of their own.
-
-+ If it is a *floating point*, say, =1.5=, it is interpreted as a multiple
-  of the base font size (there are many ways to set the main font in
-  Emacs, such as those 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/43#note_337308289][I 
documented in issue 43]], though the most robust
-  method is covered below in [[#h:ea30ff0e-3bb6-4801-baf1-d49169d94cd5][Font 
configurations for Org (and others)]]).
-+ If it is an *integer*, it is read as an absolute font height.  The
-  number is basically the point size multiplied by a hundred.  So if you
-  want it to be =18pt= you must pass =180=.
-
-Below are the variables in their default values, using the floating
-point paradigm.  The numbers are very conservative, but you are free to
-change them to your liking, such as =1.2=, =1.4=, =1.6=, =1.8=, =2.0=---or use 
a
-resource for finding a consistent scale, like 
[[https://www.modularscale.com][modularscale.com]]:
-
-#+begin_src emacs-lisp
-(setq modus-operandi-theme-scale-1 1.05
-      modus-operandi-theme-scale-2 1.1
-      modus-operandi-theme-scale-3 1.15
-      modus-operandi-theme-scale-4 1.2
-      modus-operandi-theme-scale-5 1.3)
-
-(setq modus-vivendi-theme-scale-1 1.05
-      modus-vivendi-theme-scale-2 1.1
-      modus-vivendi-theme-scale-3 1.15
-      modus-vivendi-theme-scale-4 1.2
-      modus-vivendi-theme-scale-5 1.3)
-#+end_src
-
-Note that in Org, scaling only increases the size of the heading, but
-not of keywords that are added to it, like "TODO".  This is outside the
-control of the themes and I am not aware of any way to make such
-keywords scale accordingly (see 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/37][issue 37]]).
-
-** Option for "subtle" or "intense" fringe visibility
-:PROPERTIES:
-:CUSTOM_ID: h:d989f116-7559-40bc-bf94-ef508d480960
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-fringes=
-+ =modus-vivendi-theme-fringes=
-
-Possible values:
-
-1. =nil= (default)
-2. =subtle=
-3. =intense=
-
-The "subtle" symbol will apply a greyscale background that is visible,
-yet close enough to the main background colour.  While the "intense"
-symbol will use a more noticeable greyscale background.
-
-The default is to use the same colour as that of the main background,
-meaning that the fringes are not obvious though they still occupy the
-space given to them by =fringe-mode= (8 pixels on either side by default).
-
-** Option for more slanted constructs
-:PROPERTIES:
-:CUSTOM_ID: h:cb327797-b303-47c5-8171-4587a911ccc2
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-slanted-constructs=
-+ =modus-vivendi-theme-slanted-constructs=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Choose to render more faces in slanted text (italics).  This typically
-affects documentation strings and code comments.
-
-The default is to not use italics unless it is absolutely necessary.
-
-** Option for more bold constructs
-:PROPERTIES:
-:CUSTOM_ID: h:9a77e814-5eca-488f-9a67-119a95c2d28a
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-bold-constructs=
-+ =modus-vivendi-theme-bold-constructs=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Display several constructs in bold weight.  This concerns keywords and
-other important aspects of code syntax.  It also affects certain mode
-line indicators.
-
-The default is to only use a bold weight when it is necessary.
-
-*Optionally, to define the precise weight* for bold constructs, you only
-need to change the attribute of the =bold= face.  So, assuming your
-typeface of choice supports a "semibold" weight, here is how you specify
-it throughout the theme:
-
-#+begin_src emacs-lisp
-(set-face-attribute 'bold nil :weight 'semibold)
-#+end_src
-
-** Option for "3D" or "moody" mode line
-:PROPERTIES:
-:CUSTOM_ID: h:ce155208-fdd6-4ada-9e0c-54aab7e2aff8
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-mode-line=
-+ =modus-vivendi-theme-mode-line=
-
-Possible values:
-
-1. =nil= (default)
-2. =3d=
-3. =moody=
-
-The default value (=nil=) produces a two-dimensional effect both for the
-active and inactive modelines.  The differences between the two are
-limited to distinct shades of greyscale values, with the active being
-more intense than the inactive.
-
-A =3d= symbol will make the active modeline look like a three-dimensional
-rectangle.  Inactive modelines remain 2D, though they are slightly toned
-down relative to the default.  This aesthetic is the same as what you
-get when you run Emacs without any customisations (=emacs -Q= on the
-command line).
-
-While =moody= removes all box effects from the modelines and applies
-underline and overline properties instead.  It also tones down a bit the
-inactive modelines.  This is meant to optimise things for use with the
-[[https://github.com/tarsius/moody][moody package]], though it can work fine 
even without it.
-
-** Option for desaturated or coloured-text-only diffs
-:PROPERTIES:
-:CUSTOM_ID: h:e3933a53-cbd9-4e44-958a-1d6d133f0816
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-diffs=
-+ =modus-vivendi-theme-diffs=
-
-Possible values:
-
-1. =nil= (default)
-2. =desaturated=
-2. =fg-only=
-
-By default the themes will apply richly coloured backgrounds to the
-output of diffs, such as those of =diff-mode=, =ediff=, =smerge-mode=, and
-=magit=.  These are colour combinations of an accented background and
-foreground so that, for example, added lines have a pronounced green
-background with an appropriate shade of green for the affected text.
-Word-wise or "refined" changes follow this pattern but use different
-shades of those colours to remain distinct.
-
-A =desaturated= value tones down all relevant colour values.  It still
-combines an accented background with an appropriate background, yet its
-overall impression is very subtle.  Refined changes are a bit more
-intense to fulfil their intended function, though still less saturated
-than default.
-
-While =fg-only= will remove all accented backgrounds and instead rely on
-colour-coded text to denote changes.  For instance, added lines use an
-intense green foreground, while their background is the same as the rest
-of the buffer.  Word-wise highlights still use a background value which
-is, nonetheless, more subtle than its default equivalent.
-
-Concerning =magit=, an extra set of tweaks are introduced for the effect
-of highlighting the current diff hunk, so as to remain consistent with
-the overall experience of that mode.  Expect changes that are consistent
-with the overall intent of the aforementioned.
-
-** Option for faint code syntax highlighting
-:PROPERTIES:
-:CUSTOM_ID: h:9f05eef0-9d0d-4305-98a1-c4e49f41e1c8
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-faint-syntax=
-+ =modus-vivendi-theme-faint-syntax=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Use less saturated colours in programming modes for highlighting code
-syntax.  The intent is to offer an impression of minimalism.  The
-default is to use saturated colours.
-
-Consider using the "bold constructs" and/or "slanted constructs" options
-when opting for this one.  Some packages that may further improve the
-effect of focusing on the current text are (feel free to help expand
-this list):
-
-+ 
[[https://github.com/mina86/auto-dim-other-buffers.el][auto-dim-other-buffers]]
-+ [[https://github.com/larstvei/Focus][focus]]
-+ [[https://github.com/tarsius/paren-face][paren-face]]
-
-** Option for intense line highlight (hl-line-mode)
-:PROPERTIES:
-:CUSTOM_ID: h:e19092a4-7204-40d3-ac35-3644b72de937
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-intense-hl-line=
-+ =modus-vivendi-theme-intense-hl-line=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Draw the current line of =hl-line-mode= or its global equivalent in a more
-prominent background colour.  This would also affect several packages
-that enable =hl-line-mode=, such as =elfeed= and =mu4e=.
-
-The default is to use a more subtle grey.
-
-** Option for intense parenthesis matching (show-paren-mode)
-
-Symbol names:
-
-+ =modus-operandi-theme-intense-paren-match=
-+ =modus-vivendi-theme-intense-paren-match=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Apply a more intense background to the matching parentheses (or
-delimiters).  This affects tools such as the built-in =show-paren-mode= as
-well as the =smartparens= package.  The default is to use a subtle warm
-colour for the background of those overlays.
-
-** Option for "subtle" or "intense" prompts
-:PROPERTIES:
-:CUSTOM_ID: h:53b947f7-c713-4ac2-97f7-9be44a41a67a
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-prompts=
-+ =modus-vivendi-theme-prompts=
-
-Possible values:
-
-1. =nil= (default)
-2. =subtle=
-3. =intense=
-
-The symbols "subtle" and "intense" will apply a combination of accented
-background and foreground to the minibuffer and other REPL prompts (like
-=M-x shell=).  The difference between the two is that the latter has a
-more pronounced/noticeable effect than the former.
-
-The default is to not use any background for such prompts, while only
-relying on an accented foreground colour.
-
-** Option for "moderate" or "opinionated" completion UIs
-:PROPERTIES:
-:CUSTOM_ID: h:5b0b1e66-8287-4f3f-ba14-011c29320a3f
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-completions=
-+ =modus-vivendi-theme-completions=
-
-Possible values:
-
-1. =nil= (default)
-2. =moderate=
-3. =opinionated=
-
-This is a special option that has different effects depending on the
-completion UI.  The interfaces can be grouped in two categories: (i)
-those that only or mostly use foreground colours for their interaction
-model, and (ii) those that combine background and foreground values for
-some of their metaphors.  The former category encompasses the built-in
-tools, namely, Icomplete and Ido, as well as packages like Orderless and
-Flx.  The latter covers Ivy, Helm, Selectrum, and similar.
-
-The symbol =moderate= will apply a combination of background and
-foreground that is fairly subtle.  For Icomplete and friends this
-constitutes a departure from their default aesthetics, however the
-difference is small.  While Ivy et al will appear slightly different
-than their original looks, as they are toned down a bit.
-
-The symbol =opinionated= will apply colour combinations that refashion the
-completion UI.  For the Icomplete camp this means that intense
-background and foreground combinations are used: in effect their looks
-emulate those of Ivy and co. in their original style.  Whereas the other
-group of packages will revert to an even more nuanced aesthetic with
-some additional changes to the choice of hues.
-
-To appreciate the scope of this customisation option, you should spend
-some time with every one of the =nil= (default), =moderate=, and =opinionated=
-possibilities.
-
-** Option for variable-pitch fonts in headings
-:PROPERTIES:
-:CUSTOM_ID: h:33023fa6-6482-45d4-9b5e-3c73c945718f
-:END:
-
-Symbol names:
-
-+ =modus-operandi-theme-variable-pitch-headings=
-+ =modus-vivendi-theme-variable-pitch-headings=
-
-Possible values:
-
-1. =nil= (default)
-2. =t=
-
-Choose to apply a proportionately-spaced, else "variable-pitch",
-typeface to headings (such as in Org mode).  The default is to use
-whatever the main typeface is, typically a monospaced family.
-
-Though also read [[#h:ea30ff0e-3bb6-4801-baf1-d49169d94cd5][Font 
configurations for Org (and others)]] as the themes
-are designed to cope well with more prose-friendly typeface
-configurations (e.g. using a proportionately-spaced sans-serif font for
-the main text, while letting inline code and some other space-sensitive
-constructs use a monospaced font).
-
-** Complete example configuration for the above
-:PROPERTIES:
-:CUSTOM_ID: h:0e3b8a62-8d72-4439-be2d-cb12ed98f4cb
-:END:
-
-This is a complete =use-package= declaration with Modus Operandi as an
-example.  You can modify it to your preferences.  Here we enable all
-variables /before/ loading the theme.  You can also see a different form
-of =setq= that sets the value of multiple variables at once: use one =setq=
-expression for each variable, if in doubt.
-
-*Do not forget* to =M-x package-refresh-contents= to get your package list
-up-to-date, else the initial download may fail due to a newer version
-being available.
-
-#+begin_src emacs-lisp
-(use-package modus-operandi-theme
-  :ensure t
-  :init
-  ;; NOTE: Everything is disabled by default.
-  (setq modus-operandi-theme-slanted-constructs t
-        modus-operandi-theme-bold-constructs t
-        modus-operandi-theme-fringes 'subtle ; {nil,'subtle,'intense}
-        modus-operandi-theme-3d-modeline t
-        modus-operandi-theme-faint-syntax t
-        modus-operandi-theme-intense-hl-line t
-        modus-operandi-theme-intense-paren-match t
-        modus-operandi-theme-prompts 'subtle ; {nil,'subtle,'intense}
-        modus-operandi-theme-completions 'moderate ; 
{nil,'moderate,'opinionated}
-        modus-operandi-theme-diffs 'desaturated ; {nil,'desaturated,'fg-only}
-        modus-operandi-theme-org-blocks 'greyscale ; {nil,'greyscale,'rainbow}
-        modus-operandi-theme-variable-pitch-headings t
-        modus-operandi-theme-rainbow-headings t
-        modus-operandi-theme-section-headings t
-        modus-operandi-theme-scale-headings t
-        modus-operandi-theme-scale-1 1.05
-        modus-operandi-theme-scale-2 1.1
-        modus-operandi-theme-scale-3 1.15
-        modus-operandi-theme-scale-4 1.2
-        modus-operandi-theme-scale-5 1.3)
-  :config
-  (load-theme 'modus-operandi t))
-#+end_src
-
-Need more ideas?  Check the 
[[https://protesilaos.com/dotemacs/#h:b7444e76-75d4-4ae6-a9d6-96ff9408efe6][Modus
 themes section of my dotemacs]] (though
-do not try to interpret the values of the variables, as I always test
-different combinations and scenaria).
-
-** Full access to the palette for further tweaks (advanced)
-:PROPERTIES:
-:CUSTOM_ID: h:b7282635-4fe9-415a-abdf-962b736ff5b6
-:END:
-
-Unlike the previous options which follow a straightforward pattern of
-allowing the user to quickly select their preference, the themes also
-provide a more powerful, albeit difficult, mechanism of controlling
-things with precision.
-
-*** Option 1 to redefine colour values
-:PROPERTIES:
-:CUSTOM_ID: h:149e23b6-ada1-480f-95cd-c56fb40999b5
-:END:
-
-The variables are:
-
-+ =modus-operandi-theme-override-colors-alist=
-+ =modus-vivendi-theme-override-colors-alist=
-
-Users can specify an association list that maps the names of colour
-variables to hexadecimal RGB values (in the form of =#RRGGBB=).  This
-means that it is possible to override the entire palette or subsets
-thereof (see the source code for the actual names and values).
-
-Example:
-
-#+begin_src emacs-lisp
-;; Redefine the values of those three variables for the given theme
-(setq modus-vivendi-theme-override-colors-alist
-      '(("magenta" . "#ffaabb")
-        ("magenta-alt" . "#ee88ff")
-        ("magenta-alt-other" . "#bbaaff")))
-#+end_src
-
-If you want to be creative, you can define a minor mode that refashions
-the themes on demand.  The following is a variation of what I showcased
-in the experimental 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/78][issue 78]] and is a 
simplified version of what I share
-in 
[[https://protesilaos.com/dotemacs/#h:b7444e76-75d4-4ae6-a9d6-96ff9408efe6][my 
dotemacs' section about the Modus themes]].
-
-#+begin_src emacs-lisp
-(define-minor-mode prot/modus-themes-alt-mode
-  "Override specific palette variables with custom values.
-
-This is intended as a proof-of-concept.  It is, nonetheless, a
-perfectly accessible alternative, conforming with the design
-principles of the Modus themes.  It still is not as good as the
-default colours."
-  :init-value nil
-  :global t
-  (if prot/modus-themes-alt-mode
-      (setq modus-operandi-theme-override-colors-alist
-            '(("bg-main" . "#fefcf4")
-              ("bg-dim" . "#faf6ef")
-              ("bg-alt" . "#f7efe5")
-              ("bg-hl-line" . "#f4f0e3")
-              ("bg-active" . "#e8dfd1")
-              ("bg-inactive" . "#f6ece5")
-              ("bg-region" . "#c6bab1")
-              ("bg-header" . "#ede3e0")
-              ("bg-tab-bar" . "#dcd3d3")
-              ("bg-tab-active" . "#fdf6eb")
-              ("bg-tab-inactive" . "#c8bab8")
-              ("fg-unfocused" . "#55556f"))
-            modus-vivendi-theme-override-colors-alist
-            '(("bg-main" . "#100b17")
-              ("bg-dim" . "#161129")
-              ("bg-alt" . "#181732")
-              ("bg-hl-line" . "#191628")
-              ("bg-active" . "#282e46")
-              ("bg-inactive" . "#1a1e39")
-              ("bg-region" . "#393a53")
-              ("bg-header" . "#202037")
-              ("bg-tab-bar" . "#262b41")
-              ("bg-tab-active" . "#120f18")
-              ("bg-tab-inactive" . "#3a3a5a")
-              ("fg-unfocused" . "#9a9aab")))
-    (setq modus-operandi-theme-override-colors-alist nil
-          modus-vivendi-theme-override-colors-alist nil)))
-
-(defun prot/modus-themes-toggle (&optional arg)
-  "Toggle between `prot/modus-operandi' and `prot/modus-vivendi'.
-
-With optional \\[universal-argument] prefix, enable
-`prot/modus-themes-alt-mode' for the loaded theme."
-  (interactive "P")
-  (if arg
-      (prot/modus-themes-alt-mode 1)
-    (prot/modus-themes-alt-mode -1))
-  (if (eq (car custom-enabled-themes) 'modus-operandi)
-      (progn
-        (disable-theme 'modus-operandi)
-        (load-theme 'modus-vivendi t))
-    (disable-theme 'modus-vivendi)
-    (load-theme 'modus-operandi t)))
-#+end_src
-
-*** Option 2 to apply colour variables to faces
-:PROPERTIES:
-:CUSTOM_ID: h:9754abfd-c890-4af3-91a8-1a2cb2b5be44
-:END:
-
-The macro symbols are:
-
-+ =modus-operandi-theme-with-color-variables=
-+ =modus-vivendi-theme-with-color-variables=
-
-Users can wrap face customisation snippets inside this macro in order to
-pass the variables that the themes use and map them to face attributes.
-This means that one can essentially override or extend the original
-design (also in tandem with option 1).
-
-Len Trigg who proposed 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/39][the whole idea in 
issue 39]] uses this method to
-tweak how a couple of Magit faces will look in GUI and terminal Emacs
-respectively (follow the link for screen shots and details).  This is
-Len's sample package declaration (with comments by me):
-
-#+begin_src emacs-lisp
-(use-package modus-vivendi-theme
-  :init
-  ;; enable some of the customisation options before loading the theme
-  (setq modus-vivendi-theme-visible-fringe t
-        modus-vivendi-theme-3d-modeline t)
-  :config
-  (defun customize-modus-vivendi ()
-    "Customize modus-vivendi theme"
-    (if (member 'modus-vivendi custom-enabled-themes)
-        ;; this macro allows us to access the colour palette
-        (modus-vivendi-theme-with-color-variables
-          (custom-theme-set-faces
-           'modus-vivendi
-           `(magit-branch-current
-             ((;; use a box property if the current display terminal
-               ;; supports it and also apply a background
-               ((supports :box t))
-               (:foreground ,blue-alt-other :background ,bg-alt :box t))
-              (t
-               ;; use an underline instead of a box for other terminals
-               (:foreground ,blue-alt-other :background ,bg-alt :underline 
t))))
-           `(magit-branch-remote-head
-             ((((supports :box t))
-               (:foreground ,magenta-alt-other :background ,bg-alt :box t))
-              (t
-               (:foreground ,magenta-alt-other :background ,bg-alt :underline 
t))))
-           ))))
-  ;; invoke the above function when appropriate in order to override the
-  ;; styles of the desired faces
-  (add-hook 'after-load-theme-hook 'customize-modus-vivendi)
-  ;; load the theme
-  (load-theme 'modus-vivendi t))
-#+end_src
-
-Perhaps you want something simpler, such as a nice style for the cursor:
-
-#+begin_src emacs-lisp
-(modus-operandi-theme-with-color-variables
-  (custom-theme-set-faces
-   'modus-operandi
-   `(cursor ((t (:background ,blue-alt))))))
-
-(modus-vivendi-theme-with-color-variables
-  (custom-theme-set-faces
-   'modus-vivendi
-   `(cursor ((t (:background ,green-alt))))))
-#+end_src
-
-The code for the bespoke =after-load-theme-hook= could be something like
-the following (courtesy of the 
[[https://github.com/seagle0128/.emacs.d/blob/master/lisp/init-funcs.el][Centaur
 Emacs project]]):
-
-#+begin_src emacs-lisp
-(defvar after-load-theme-hook nil
-  "Hook run after a color theme is loaded using `load-theme'.")
-
-(defun run-after-load-theme-hook (&rest _)
-  "Run `after-load-theme-hook'."
-  (run-hooks 'after-load-theme-hook))
-
-(advice-add #'load-theme :after #'run-after-load-theme-hook)
-#+end_src
-
-If you need more ideas check how I configure the themes in 
[[https://gitlab.com/protesilaos/dotemacs][my dotemacs]].
-If something is not clear or not working as intended, please let me
-know.
-
-*** Further considerations
-:PROPERTIES:
-:CUSTOM_ID: h:4acda0f1-564e-48ff-8998-ebf7618377dd
-:END:
-
-Please understand that these customisation methods are meant for
-advanced users or those who are prepared to do their own research.  If
-you think that the themes do not work well in some context you can
-inform me about it: maybe you do not need to carry your own
-customisations.  We can just fix the issue in its source.
-
-To harness the potential of this method you will need to study the
-source code of the themes.  You can always open an issue in case you
-need some help.  To support you in this task, try the =rainbow-mode=
-package which offers live colour previews.  This is how I configure it:
-
-#+begin_src emacs-lisp
-(use-package rainbow-mode
-  :ensure
-  :diminish                             ; optional if you use `diminish'
-  :commands rainbow-mode                ; optional
-  :config
-  (setq rainbow-ansi-colors nil)
-  (setq rainbow-x-colors nil))
-#+end_src
-
-As for the means to check the contrast in perceived luminance between a
-foreground colour and its expected background combination, refer to the
-methods documented in my 
[[https://protesilaos.com/codelog/2020-05-10-modus-operandi-palette-review/][Modus
 Operandi theme subtle palette review]]
-(2020-05-10).
-
-** Font configurations for Org (and others)
-:PROPERTIES:
-:CUSTOM_ID: h:ea30ff0e-3bb6-4801-baf1-d49169d94cd5
-:END:
-
-The themes are designed to cope well with mixed font settings.
-Currently this applies to =org-mode= (courtesy of 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/40][Ben in issue 40]]) 
and
-=markdown-mode=.
-
-In practice it means that the user can safely opt for a more
-prose-friendly proportionately-spaced typeface as their default for
-paragraphs and headings, while allowing spacing-sensitive elements like
-tables and inline code to always use a monospaced font.  Users can try
-the built-in function of Emacs called =variable-pitch-mode=.  This is to
-ensure that code blocks, tables, and other relevant elements use the
-appropriate type settings and are positioned correctly.
-
-*To make everything use your desired font families*, you need to configure
-the =variable-pitch= (proportional spacing) and =fixed-pitch= (monospaced)
-faces respectively.  Otherwise you may get unintended combinations (such
-as those experienced by Mark in 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/42][issue 42]] or what I 
documented at length
-in [[https://gitlab.com/protesilaos/modus-themes/-/issues/54][issue 54]]).
-
-Put something like this in your initialisation file:
-
-#+begin_src emacs-lisp
-(set-face-attribute 'variable-pitch nil :family "DejaVu Sans" :height 110)
-(set-face-attribute 'fixed-pitch nil :family "Source Code Pro" :height 110)
-#+end_src
-
-You can also set your standard font the same way.  For example:
-
-#+begin_src emacs-lisp
-(set-face-attribute 'default nil :family "Fira Code" :height 120)
-#+end_src
-
-The value of the =:height= attribute essentially is the point size × 100.
-So if you want to use Fira Code at point size =12=, you set the height to
-=120=.  Values do not need to be rounded to multiples of ten, so the likes
-of =125= are perfectly valid.
-
-*Alternatively* you may want to review my elaborate setup for fonts,
-focused writing, etc.  Start with the 
[[https://protesilaos.com/dotemacs/#h:7a4dd5b8-724d-4f7c-b5ee-01d8ac98bda9][Base
 font configurations]] of my
-dotemacs (includes documentation and code).  For video demonstrantions
-check these:
-
-+ 
[[https://protesilaos.com/codelog/2020-07-16-emacs-focused-editing/][“Focused 
editing” tools for Emacs]] (2020-07-16)
-+ 
[[https://protesilaos.com/codelog/2020-07-17-emacs-mixed-fonts-org/][Configuring
 mixed fonts for Org mode and others]] (2020-07-17)
-
-* Face coverage
-:PROPERTIES:
-:CUSTOM_ID: h:944a3bdf-f545-40a0-a26c-b2cec8b2b316
-:END:
-
-This list will always be updated to reflect the current state of the
-project.  The idea is to offer an overview of the /known status/ of all
-affected face groups.
-
-** Full support
-:PROPERTIES:
-:CUSTOM_ID: h:5ea98392-1376-43a4-8080-2d42a5b690ef
-:END:
-
-The items with an appended asterisk =*= tend to have lots of extensions, so
-the "full support" may not be 100% true…
-
-+ ace-window
-+ ag
-+ alert
-+ all-the-icons
-+ annotate
-+ anzu
-+ apropos
-+ apt-sources-list
-+ artbollocks-mode
-+ auctex and TeX
-+ auto-dim-other-buffers
-+ avy
-+ awesome-tray
-+ bm
-+ bongo
-+ boon
-+ breakpoint (provided by the built-in =gdb-mi.el= library)
-+ buffer-expose
-+ calendar and diary
-+ calfw
-+ centaur-tabs
-+ change-log and log-view (=vc-print-log= and =vc-print-root-log=)
-+ cider
-+ circe
-+ color-rg
-+ column-enforce-mode
-+ company-mode*
-+ company-posframe
-+ compilation-mode
-+ completions
-+ counsel*
-+ counsel-css
-+ counsel-notmuch
-+ counsel-org-capture-string
-+ cov
-+ csv-mode
-+ ctrlf
-+ custom (=M-x customize=)
-+ dap-mode
-+ dashboard (emacs-dashboard)
-+ deadgrep
-+ debbugs
-+ define-word
-+ deft
-+ dictionary
-+ diff-hl
-+ diff-mode
-+ dim-autoload
-+ dired
-+ dired-async
-+ dired-git
-+ dired-git-info
-+ dired-narrow
-+ dired-subtree
-+ diredfl
-+ disk-usage
-+ doom-modeline
-+ dynamic-ruler
-+ easy-jekyll
-+ easy-kill
-+ ebdb
-+ ediff
-+ eglot
-+ el-search
-+ eldoc
-+ eldoc-box
-+ elfeed
-+ elfeed-score
-+ emms
-+ enhanced-ruby-mode
-+ epa
-+ equake
-+ erc
-+ eros
-+ ert
-+ eshell
-+ eshell-fringe-status
-+ eshell-git-prompt
-+ eshell-prompt-extras (epe)
-+ evil* (evil-mode)
-+ evil-goggles
-+ evil-visual-mark-mode
-+ eww
-+ eyebrowse
-+ fancy-dabbrev
-+ flycheck
-+ flycheck-indicator
-+ flycheck-posframe
-+ flymake
-+ flyspell
-+ flyspell-correct
-+ flx
-+ freeze-it
-+ frog-menu
-+ focus
-+ fold-this
-+ font-lock (generic syntax highlighting)
-+ forge
-+ fountain (fountain-mode)
-+ geiser
-+ git-commit
-+ git-gutter (and variants)
-+ git-lens
-+ git-rebase
-+ git-timemachine
-+ git-walktree
-+ gnus
-+ golden-ratio-scroll-screen
-+ helm* (also see [[#h:e4408911-e186-4825-bd4f-4d0ea55cd6d6][section below on 
Helm's grep-related functions]])
-+ helm-ls-git
-+ helm-switch-shell
-+ helm-xref
-+ helpful
-+ highlight-blocks
-+ highlight-defined
-+ highlight-escape-sequences (=hes-mode=)
-+ highlight-indentation
-+ highlight-numbers
-+ highlight-symbol
-+ highlight-tail
-+ highlight-thing
-+ hl-defined
-+ hl-fill-column
-+ hl-line-mode
-+ hl-todo
-+ hydra
-+ hyperlist
-+ ibuffer
-+ icomplete
-+ icomplete-vertical
-+ ido-mode
-+ iedit
-+ iflipb
-+ imenu-list
-+ indium
-+ info
-+ info-colors
-+ interaction-log
-+ ioccur
-+ isearch, occur, etc.
-+ ivy*
-+ ivy-posframe
-+ jira (org-jira)
-+ journalctl-mode
-+ js2-mode
-+ julia
-+ jupyter
-+ kaocha-runner
-+ keycast
-+ line numbers (=display-line-numbers-mode= and global variant)
-+ lsp-mode
-+ lsp-ui
-+ magit
-+ magit-imerge
-+ man
-+ markdown-mode
-+ markup-faces (=adoc-mode=)
-+ mentor
-+ messages
-+ minibuffer-line
-+ minimap
-+ modeline
-+ mood-line
-+ moody (read [[#h:ce155208-fdd6-4ada-9e0c-54aab7e2aff8][Option for "3D" or 
"moody" mode line]])
-+ mu4e
-+ mu4e-conversation
-+ multiple-cursors
-+ neotree
-+ no-emoji
-+ notmuch
-+ num3-mode
-+ nxml-mode
-+ objed
-+ orderless
-+ org*
-+ org-journal
-+ org-noter
-+ org-pomodoro
-+ org-recur
-+ org-roam
-+ org-superstar
-+ org-table-sticky-header
-+ org-treescope
-+ origami
-+ outline-mode
-+ outline-minor-faces
-+ package (=M-x list-packages=)
-+ page-break-lines
-+ paradox
-+ paren-face
-+ parrot
-+ pass
-+ persp-mode
-+ perspective
-+ phi-grep
-+ phi-search
-+ pkgbuild-mode
-+ pomidor
-+ powerline
-+ powerline-evil
-+ proced
-+ prodigy
-+ rainbow-blocks
-+ rainbow-identifiers
-+ rainbow-delimiters
-+ rcirc
-+ regexp-builder (also known as =re-builder=)
-+ rg (rg.el)
-+ ripgrep
-+ rmail
-+ ruler-mode
-+ sallet
-+ selectrum
-+ semantic
-+ sesman
-+ shell-script-mode
-+ show-paren-mode
-+ side-notes
-+ skewer-mode
-+ smart-mode-line
-+ smartparens
-+ smerge
-+ spaceline
-+ speedbar
-+ spell-fu
-+ stripes
-+ suggest
-+ switch-window
-+ swiper
-+ swoop
-+ sx
-+ symbol-overlay
-+ syslog-mode
-+ table (built-in table.el)
-+ telephone-line
-+ term
-+ tomatinho
-+ transient (pop-up windows such as Magit's)
-+ trashed
-+ treemacs
-+ tty-menu
-+ tuareg
-+ undo-tree
-+ vc (built-in mode line status for version control)
-+ vc-annotate (=C-x v g=)
-+ vdiff
-+ vimish-fold
-+ visible-mark
-+ visual-regexp
-+ volatile-highlights
-+ vterm
-+ wcheck-mode
-+ web-mode
-+ wgrep
-+ which-function-mode
-+ which-key
-+ whitespace-mode
-+ window-divider-mode
-+ winum
-+ writegood-mode
-+ woman
-+ xah-elisp-mode
-+ xref
-+ xterm-color (and ansi-colors)
-+ yaml-mode
-+ yasnippet
-+ ztree
-
-Plus many other miscellaneous faces that are provided by the upstream
-GNU Emacs distribution.
-
-** Covered but not styled explicitly
-:PROPERTIES:
-:CUSTOM_ID: h:8ada963d-046d-4c67-becf-eee18595f902
-:END:
-
-These do not require any extra styles because they are configured to
-inherit from some basic faces.  Please confirm.
-
-+ edit-indirect
-+ php-mode
-+ swift-mode
-
-** Will NOT be supported
-:PROPERTIES:
-:CUSTOM_ID: h:46756fcc-0d85-4f77-b0e3-64f890e1c2ea
-:END:
-
-I have thus far identified a single package that does fit into the
-overarching objective of this project: 
[[https://github.com/hlissner/emacs-solaire-mode][solaire]].  It basically 
tries to
-cast a less intense background on the main file-visiting buffers, so
-that secondary elements like sidebars can have the default (pure
-white/black) background.
-
-/I will only support this package if it ever supports the inverse
-effect/: less intense colours (but still accessible) for supportive
-interfaces and the intended styles for the content you are actually
-working on.
-
-** Note for powerline or spaceline users
-:PROPERTIES:
-:CUSTOM_ID: h:a7d956e5-c4fa-4586-bd84-770bf2c16666
-:END:
-
-After making changes to the theme configuration, in order to reset any
-color irregularities in the mode line, both Powerline and Spaceline
-package users can use the command =powerline-reset=.
-
-** Note on colour rendering of HTML buffers
-:PROPERTIES:
-:CUSTOM_ID: h:61875051-b284-40f0-a74d-1574f41b3d42
-:END:
-
-Emacs' HTML rendering mechanism (=shr=) may need explicit configuration to
-respect the theme's colours instead of whatever specifications the
-webpage provides.  Consult =C-h v shr-use-colors=.  This has been
-demonstrated in 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/60][issue 60]] with 
respect to viewing mails in mu4e.
-
-** Note for HELM users of grep or grep-like functions
-:PROPERTIES:
-:CUSTOM_ID: h:e4408911-e186-4825-bd4f-4d0ea55cd6d6
-:END:
-
-There is one face from the Helm package that is meant to highlight the
-matches of a grep or grep-like command (=ag= or =ripgrep=).  It is
-=helm-grep-match=.  However, this face can only apply when the user does
-not pass =--color=always= as a command-line option for their command.
-
-Here is the docstring for that face, which is defined in the
-=helm-grep.el= library (view a library with =M-x find-library=).
-
-#+begin_quote
-Face used to highlight grep matches. Have no effect when grep backend
-use "--color="
-#+end_quote
-
-The user must either remove =--color= from the flags passed to the grep
-function, or explicitly use =--color=never= (or equivalent).  Helm
-provides user-facing customisation options for controlling the grep
-function's parameters, such as =helm-grep-default-command= and
-=helm-grep-git-grep-command=.
-
-When =--color=always= is in effect, the grep output will use red text in
-bold letter forms to present the matching part in the list of
-candidates.  *That style still meets the contrast ratio target of >= 7:1*
-(accessibility standard WCAG AAA), because it draws the reference to
-ANSI colour number 1 (red) from the already-supported array of
-=ansi-color-names-vector=.
-
-I presented 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/21#note_302748582][some 
screen shots of this in issue 21]].
-
-A similar scenario was 
[[https://gitlab.com/protesilaos/modus-themes/-/issues/49][also encountered in 
issue 49]] which was promptly
-fixed by the Helm maintainer.
-
-** Note on VC-ANNOTATE-BACKGROUND-MODE
-:PROPERTIES:
-:CUSTOM_ID: h:5b5d4420-50cc-4d53-a9f8-825cba6b68f1
-:END:
-
-Due to the unique way =vc-annotate= (=C-x v g=) applies colours, support for
-its background mode (=vc-annotate-background-mode=) is disabled at the
-theme level.
-
-Normally, such a drastic measure should not belong in a theme: assuming
-the user's preferences is bad practice.  However, it has been deemed
-necessary in the interest of preserving colour contrast accessibility
-while still supporting a useful built-in tool.
-
-If there actually is a way to avoid such a course of action, without
-prejudice to the accessibility standard of this project, then please
-report as much (or send patches, per the information in the 
[[#h:25ba8d6f-6604-4338-b774-bbe531d467f6][Contributing]]
-section).
-
-** Note about the themes that are built into Emacs
-:PROPERTIES:
-:CUSTOM_ID: h:064dc3f2-ef1f-448e-bb11-0efb37884ebe
-:END:
-
-As mentioned in the section about 
[[#h:c3e293e8-8464-4196-aefd-184027116ded][installing the packages]], the themes
-are now bundled with the upstream Emacs distribution.  Their version is
-that of the latest tagged release.  This is because I do not have push
-privileges to the Emacs repository and must contact the mailing list for
-someone else to make the changes for me.  As you can understand, it
-would be too tedious to do this each time I make a commit.
-
-If I am ever granted access to the Emacs git repo, I will make sure that
-the built-in themes are synced with the =HEAD= of my =master= branch.
-
-* Contributing
-:PROPERTIES:
-:CUSTOM_ID: h:25ba8d6f-6604-4338-b774-bbe531d467f6
-:END:
-
-A few tasks you can help me with:
-
-+ Suggest refinements to packages that are covered.
-+ Report packages not covered thus far.
-+ Report bugs, inconsistencies, shortcomings.
-+ Help expand the documentation of covered-but-not-styled packages.
-+ Suggest refinements to the colour palette.
-+ Help expand this document or any other piece of documentation.
-
-It would be great if your feedback also includes some screenshots, GIFs,
-or short videos.  Though this is not a requirement.
-
-Whatever you do, please bear in mind the overarching objective of the
-Modus themes: to keep a contrast ratio that is greater or equal to 7:1
-between background and foreground colours.  If a compromise is ever
-necessary between aesthetics and accessibility, it shall always be made
-in the interest of the latter.
-
-** Code contributions require copyright assignment to the FSF
-:PROPERTIES:
-:CUSTOM_ID: h:d3fb2fc7-6c34-4e68-b2d6-6048849b0319
-:END:
-
-I accept code contributions as well (send merge requests!).  But for any
-major contribution (more than 15 lines, or so, in aggregate), you need
-to make a copyright assignment to the Free Software Foundation.  This is
-necessary because the themes are distributed through the official GNU
-ELPA repository and the FSF must be in a position to enforce the GNU
-General Public License.
-
-Copyright assignment /is a simple process/ that I had to follow as well.
-Check the 
[[https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future][request
 form]].  You must write an email to the address
-mentioned in the form and then wait for the FSF to send you a legal
-agreement.  Sign the document and file it back to them.  This should all
-happen via email and take about a week.
-
-I encourage you to go through this process.  You only need to do it
-once.  It will allow you to make contributions to Emacs in general.
-
-* External projects (ports)
-:PROPERTIES:
-:CUSTOM_ID: h:2a473296-2dd4-4575-9991-b89f83ef70aa
-:END:
-
-The present section documents projects that extend the scope of the
-Modus themes.  The following list will be updated whenever relevant
-information is brought to my attention.  If you already have or intend
-to produce such a port, feel welcome [[https://protesilaos.com/contact][to 
contact me]].
-
-+ Modus exporter :: This is [[https://github.com/polaris64/modus-exporter][an 
Elisp library written by Simon Pugnet]].
-  It is meant to capture the colour values of the active Modus theme
-  (Operandi or Vivendi) and output it as a valid theme for some other
-  application.  As of this writing (2020-08-18), the project supports
-  exporting to a valid yaml format that can be applied to the Alacritty
-  terminal emulator.  Other templates are expected to be made available
-  in the near future.
-
-* Meta
-:PROPERTIES:
-:CUSTOM_ID: h:4c338a51-509e-42c0-8820-1f5014fb477b
-:END:
-
-If you are curious about the principles that govern the development of
-this project, read my article 
[[https://protesilaos.com/codelog/2020-03-17-design-modus-themes-emacs/][On the 
design of the Modus themes]]
-(2020-03-17).
-
-Here are some more publications for those interested in the kind of work
-that goes into this project:
-
-+ 
[[https://protesilaos.com/codelog/2020-05-10-modus-operandi-palette-review/][Modus
 Operandi theme subtle palette review]] (2020-05-10)
-+ 
[[https://protesilaos.com/codelog/2020-06-13-modus-vivendi-palette-review/][Modus
 Vivendi theme subtle palette review]] (2020-06-13)
-+ 
[[https://protesilaos.com/codelog/2020-07-04-modus-themes-faint-colours/][Modus 
themes: new "faint syntax" option]] (2020-07-04)
-+ 
[[https://protesilaos.com/codelog/2020-07-08-modus-themes-nuanced-colours/][Modus
 themes: major review of "nuanced" colours]] (2020-07-08)
-
-* COPYING
-:PROPERTIES:
-:CUSTOM_ID: h:66652183-2fe0-46cd-b4bb-4121bad78d57
-:END:
-
-The Modus Themes are distributed under the terms of the GNU General
-Public License version 3 or, at your choice, any later version.  See the
-COPYING file distributed in the 
[[https://gitlab.com/protesilaos/modus-themes][project's Git repository]].