[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/modus-themes f4237bdb02 1/2: Update development links
|
From: |
ELPA Syncer |
|
Subject: |
[elpa] externals/modus-themes f4237bdb02 1/2: Update development links |
|
Date: |
Wed, 17 Jan 2024 00:59:17 -0500 (EST) |
branch: externals/modus-themes
commit f4237bdb028dffc72397e526fca4cec2a8d59031
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>
Update development links
---
README.md | 10 +-
doc/modus-themes.info | 567 +++++++++++++++++------------------
doc/modus-themes.org | 12 +-
modus-operandi-deuteranopia-theme.el | 5 +-
modus-operandi-theme.el | 5 +-
modus-operandi-tinted-theme.el | 5 +-
modus-operandi-tritanopia-theme.el | 5 +-
modus-themes.el | 5 +-
modus-vivendi-deuteranopia-theme.el | 5 +-
modus-vivendi-theme.el | 5 +-
modus-vivendi-tinted-theme.el | 5 +-
modus-vivendi-tritanopia-theme.el | 5 +-
12 files changed, 309 insertions(+), 325 deletions(-)
diff --git a/README.md b/README.md
index 619235e9bb..b90a2dc07b 100644
--- a/README.md
+++ b/README.md
@@ -25,9 +25,7 @@ the themes across the years.
+ Change log: <https://protesilaos.com/emacs/modus-themes-changelog>
+ Colour palette: <https://protesilaos.com/emacs/modus-themes-colors>
+ Sample pictures: <https://protesilaos.com/emacs/modus-themes-pictures>
-+ Git repo on SourceHut: <https://git.sr.ht/~protesilaos/modus-themes>
- - Mirrors:
- + GitHub: <https://github.com/protesilaos/modus-themes>
- + GitLab: <https://gitlab.com/protesilaos/modus-themes>
-+ Mailing list: <https://lists.sr.ht/~protesilaos/modus-themes>
-+ Backronym: My Old Display Unexpectedly Sharpened ... themes
++ Git repositories:
+ + GitHub: <https://github.com/protesilaos/modus-themes>
+ + GitLab: <https://gitlab.com/protesilaos/modus-themes>
++ Backronym: My Old Display Unexpectedly Sharpened ... themes.
diff --git a/doc/modus-themes.info b/doc/modus-themes.info
index 7b65b5f9b5..70914c0535 100644
--- a/doc/modus-themes.info
+++ b/doc/modus-themes.info
@@ -1,4 +1,4 @@
-This is modus-themes.info, produced by makeinfo version 7.1 from
+This is modus-themes.info, produced by makeinfo version 6.8 from
modus-themes.texi.
Copyright (C) 2020-2023 Free Software Foundation, Inc.
@@ -52,16 +52,13 @@ as such.
• Package name (GNU ELPA): ‘modus-themes’
• Official manual: <https://protesilaos.com/emacs/modus-themes>
• Change log: <https://protesilaos.com/emacs/modus-themes-changelog>
- • Color palette: <https://protesilaos.com/emacs/modus-themes-colors>
+ • Colour palette: <https://protesilaos.com/emacs/modus-themes-colors>
• Sample pictures:
<https://protesilaos.com/emacs/modus-themes-pictures>
- • Git repo on SourceHut:
- <https://git.sr.ht/~protesilaos/modus-themes>
- • Mirrors:
- • GitHub: <https://github.com/protesilaos/modus-themes>
- • GitLab: <https://gitlab.com/protesilaos/modus-themes>
- • Mailing list: <https://lists.sr.ht/~protesilaos/modus-themes>
- • Backronym: My Old Display Unexpectedly Sharpened ... themes
+ • Git repositories:
+ • GitHub: <https://github.com/protesilaos/modus-themes>
+ • GitLab: <https://gitlab.com/protesilaos/modus-themes>
+ • Backronym: My Old Display Unexpectedly Sharpened ... themes.
* Menu:
@@ -78,7 +75,7 @@ as such.
* GNU Free Documentation License::
* Indices::
--- The Detailed Node Listing --
+— The Detailed Node Listing —
Overview
@@ -237,11 +234,11 @@ distance in relative luminance of 7:1.
subgroups.
Main themes
- ‘modus-operandi’ is the project's main light theme, while
+ ‘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
+ reference for what a highly legible “default” theme should look
like.
Tinted themes
@@ -316,7 +313,7 @@ File: modus-themes.info, Node: Installation, Next: Enable
and load, Prev: Ove
**************
The Modus themes are distributed with Emacs starting with version 28.1.
-On older versions of Emacs, they can be installed using Emacs' package
+On older versions of Emacs, they can be installed using Emacs’ package
manager or manually from their code repository. There also exist
packages for distributions of GNU/Linux.
@@ -324,7 +321,7 @@ packages for distributions of GNU/Linux.
includes version ‘3.0.0’. Emacs 30 provides a newer, refactored version
that thoroughly refashions how the themes are implemented and
customized. Such major versions are not backward-compatible due to the
-limited resources at the maintainer's disposal to support multiple
+limited resources at the maintainer’s disposal to support multiple
versions of Emacs and of the themes across the years.
* Menu:
@@ -349,7 +346,7 @@ stored in ‘~/.emacs.d’ and that you want to place the Modus
themes in
$ git clone https://gitlab.com/protesilaos/modus-themes.git
~/.emacs.d/modus-themes
- 1. Add that path to your known Elisp libraries' list, by placing this
+ 1. Add that path to your known Elisp libraries’ list, by placing this
snippet of Emacs Lisp in your init file (e.g. ‘init.el’):
(add-to-list 'load-path "~/.emacs.d/modus-themes")
@@ -381,7 +378,7 @@ File: modus-themes.info, Node: Install on GNU/Linux,
Next: Dealing with byte c
The themes are also available from the archives of some distributions of
GNU/Linux. 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.
+distro’s packaging policies.
* Menu:
@@ -400,7 +397,7 @@ The themes are part of Debian 11 Bullseye. Get them with:
They are now ready to be used: *note Enable and load::.
- NOTE that Debian's package is severely out-of-date as of this writing
+ NOTE that Debian’s package is severely out-of-date as of this writing
2022-07-24 09:57 +0300.
@@ -643,7 +640,7 @@ package configurations in their setup. We use this as an
example:
*note Differences between loading and enabling::.
Note: make sure not to customize the variable
-‘custom-theme-load-path’ or ‘custom-theme-directory’ after the themes'
+‘custom-theme-load-path’ or ‘custom-theme-directory’ after the themes’
package declaration. That will lead to failures in loading the files.
If either or both of those variables need to be changed, their values
should be defined before the package declaration of the themes.
@@ -657,7 +654,7 @@ File: modus-themes.info, Node: Differences between loading
and enabling, Prev:
============================================
The reason we recommend ‘load-theme’ instead of the other option of
-‘enable-theme’ is that the former does a kind of "reset" on the face
+‘enable-theme’ is that the former does a kind of “reset” on the face
specs. It quite literally loads (or reloads) the theme. Whereas the
‘enable-theme’ function simply puts an already loaded theme to the top
of the list of enabled items, re-using whatever state was last loaded.
@@ -673,7 +670,7 @@ so it might appear to the unsuspecting user that the themes
are somehow
broken whenever they try to assign a new value to a customization option
or some face.
- This "reset" that ‘load-theme’ brings about does, however, come at
+ This “reset” that ‘load-theme’ brings about does, however, come at
the cost of being somewhat slower than ‘enable-theme’. Users who have a
stable setup and who seldom update their variables during a given Emacs
session, are better off using something like this:
@@ -972,7 +969,7 @@ symbols:
The default (a ‘nil’ value or an empty list) means to only use a
subtle colored foreground color.
- The ‘italic’ property adds a slant to the font's forms (italic or
+ The ‘italic’ property adds a slant to the font’s forms (italic or
oblique forms, depending on the typeface).
The symbol of a font weight attribute such as ‘light’, ‘semibold’, et
@@ -1015,7 +1012,7 @@ Here is a sample, followed by a description of the
particularities:
(selection . (semibold italic))))
The ‘matches’ key refers to the highlighted characters that
-correspond to the user's input. When its properties are ‘nil’ or an
+correspond to the user’s input. When its properties are ‘nil’ or an
empty list, matching characters in the user interface will have a bold
weight and a colored foreground. The list of properties may include any
of the following symbols regardless of the order they may appear in:
@@ -1081,22 +1078,22 @@ this case, the delimiter lines have a gray color for
their text, making
them look exactly like all other Org properties.
Option ‘gray-background’ applies a subtle gray background to the
-block's contents. It also affects the begin and end lines of the block
+block’s contents. It also affects the begin and end lines of the block
as they get another shade of gray as their background, which
differentiates them from the contents of the block. All background
colors extend to the edge of the window, giving the area a rectangular,
-"blocky" presentation. If the begin/end lines do not extend in this
+“blocky” presentation. If the begin/end lines do not extend in this
way, check the value of the Org user option
‘org-fontify-whole-block-delimiter-line’.
Option ‘tinted-background’ uses a colored background for the contents
of the block. The exact color value will depend on the programming
language and is controlled by the variable ‘org-src-block-faces’ (refer
-to the theme's source code for the current association list). For this
+to the theme’s source code for the current association list). For this
to take effect, the Org buffer needs to be restarted with
‘org-mode-restart’.
- Code blocks use their major mode's fontification (syntax
+ Code blocks use their major mode’s fontification (syntax
highlighting) only when the variable ‘org-src-fontify-natively’ is
non-‘nil’. While quote/verse blocks require setting
‘org-fontify-quote-and-verse-blocks’ to a non-‘nil’ value.
@@ -1106,7 +1103,7 @@ non-‘nil’. While quote/verse blocks require setting
File: modus-themes.info, Node: Heading styles, Next: UI typeface, Prev: Org
mode blocks, Up: Customization options
-4.10 Option for the headings' overall style
+4.10 Option for the headings’ overall style
===========================================
Brief: Heading styles with optional list of values per heading level.
@@ -1114,7 +1111,7 @@ Brief: Heading styles with optional list of values per
heading level.
Symbol: ‘modus-themes-headings’ (‘alist’ type, multiple properties)
This is an alist that accepts a ‘(KEY . LIST-OF-VALUES)’ combination.
-The ‘KEY’ is either a number, representing the heading's level (0
+The ‘KEY’ is either a number, representing the heading’s level (0
through 8) or ‘t’, which pertains to the fallback style. The named keys
‘agenda-date’ and ‘agenda-structure’ apply to the Org agenda.
@@ -1295,7 +1292,7 @@ the color value that corresponds to the active theme
(e.g. make the
cursor ‘blue-warmer’ in all themes, whatever the value of ‘blue-warmer’
is in each theme).
- The value of any overrides' variable must mirror a theme's palette.
+ The value of any overrides’ variable must mirror a theme’s palette.
Palette variables are named after their theme as ‘THEME-NAME-palette’.
For example, the ‘modus-operandi-palette’ is like this:
@@ -1376,7 +1373,7 @@ options.).
This section is of interest only to users who are prepared to
maintain their own local tweaks and who are willing to deal with any
possible incompatibilities between versioned releases of the themes. As
-such, they are labeled as "do-it-yourself" or "DIY".
+such, they are labeled as “do-it-yourself” or “DIY”.
* Menu:
@@ -1434,7 +1431,7 @@ colors are desaturated. It makes the themes less
attention-grabbing.
colors accented instead of gray and increases coloration in a number of
places. Colors stand out more and are made easier to spot.
- For some stylistic variation try the "cooler" and "warmer" presets:
+ For some stylistic variation try the “cooler” and “warmer” presets:
;; This:
(setq modus-themes-common-palette-overrides
modus-themes-preset-overrides-cooler)
@@ -1647,7 +1644,7 @@ File: modus-themes.info, Node: Make the fringe invisible
or another color, Nex
This is one of our practical examples to override the semantic colors of
the Modus themes (*note Stylistic variants using palette overrides::).
Here we show how to make the fringe invisible or how to assign to it a
-different color. The "fringe" is a small area to the right and left
+different color. The “fringe” is a small area to the right and left
side of the Emacs window which shows indicators such as for truncation
or continuation lines.
@@ -1826,7 +1823,7 @@ the Modus themes (*note Stylistic variants using palette
overrides::).
In previous versions of the themes, we provided an option for yellow-ish
comments and green-ish strings. For some users, those were still not
good enough, as the exact values were hardcoded. Here we show how to
-reproduce the effect, but also how to tweak it to one's liking.
+reproduce the effect, but also how to tweak it to one’s liking.
*note Make code syntax use the old alt-syntax style::.
@@ -1868,7 +1865,7 @@ the Modus themes (*note Stylistic variants using palette
overrides::).
In this section we show how to reproduce what previous versions of the
Modus themes provided as a stylistic alternative for code syntax. The
upside of using overrides for this purpose is that we can tweak the
-style to our liking, but first let's start with its recreation:
+style to our liking, but first let’s start with its recreation:
;; These overrides are common to all Modus themes. We also provide
;; theme-specific options, such as `modus-operandi-palette-overrides'.
@@ -1895,7 +1892,7 @@ style to our liking, but first let's start with its
recreation:
(rx-construct magenta-warmer)
(rx-backslash blue-cooler)))
- The "alt-syntax" could optionally use green strings and yellow
+ The “alt-syntax” could optionally use green strings and yellow
comments (*note Make comments yellow and strings green::):
;; Same as above, but with yellow comments and green strings
@@ -1914,7 +1911,7 @@ comments (*note Make comments yellow and strings green::):
(rx-construct magenta-warmer)
(rx-backslash blue-cooler)))
- The standard "alt-syntax" has red strings. As such, it is
+ The standard “alt-syntax” has red strings. As such, it is
interesting to experiment with faintly red colored comments:
;; Like the old "alt-syntax" but with faint red comments
@@ -2262,7 +2259,7 @@ File: modus-themes.info, Node: Make inline code in prose
use alternative styles
This is one of our practical examples to override the semantic colors of
the Modus themes (*note 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
+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 permutation.
@@ -2530,7 +2527,7 @@ only use color-coded text without any added background.
What we
basically do is to disable the applicable backgrounds and then intensify
the foregrounds. Since the deuteranopia-optimized themes do not use the
red-green color coding, we make an extra set of adjustments for them by
-overriding their palettes directly instead of just using the "common"
+overriding their palettes directly instead of just using the “common”
overrides.
;; Diffs with only foreground colors. Word-wise ("refined") diffs
@@ -2596,8 +2593,8 @@ color coding for diffs, defaulting instead to yellow+blue
which are
discernible. Users with deuteranomaly or, generally, those who like a
different aesthetic, can use the following to make diffs use the
red+yellow+blue color coding for removed, changed, and added lines
-respectively. This is achieved by overriding the "changed" and
-"removed" entries to use the colors of regular ‘modus-operandi’ and
+respectively. This is achieved by overriding the “changed” and
+“removed” entries to use the colors of regular ‘modus-operandi’ and
‘modus-vivendi’.
(setq modus-operandi-deuteranopia-palette-overrides
@@ -2745,8 +2742,8 @@ expand these findings. ]
The graphical version of Emacs can reproduce color values accurately.
Whereas things get more tricky when Emacs is used in a terminal
-emulator, because the terminals' own capabilities determine the number
-of colors that may be displayed: the Modus themes don't look as good in
+emulator, because the terminals’ own capabilities determine the number
+of colors that may be displayed: the Modus themes don’t look as good in
that case.
There is, however, a way to instruct supported terminal emulators to
@@ -2775,17 +2772,17 @@ expand these findings. ]
When Emacs runs in a non-windowed session its color reproduction
capacity is framed or determined by the underlying terminal emulator
(*note More accurate colors in terminal emulators::). Emacs cannot
-produce a color that lies outside the range of what the terminal's color
+produce a color that lies outside the range of what the terminal’s color
palette renders possible.
- This is immediately noticeable when the terminal's first 16 codes do
+ This is immediately noticeable when the terminal’s first 16 codes do
not include a pure black value for the ‘termcol0’ entry and a pure white
for ‘termcol15’. Emacs cannot set the correct background (white for
‘modus-operandi’; black for ‘modus-vivendi’) or foreground (inverse of
the background). It thus falls back to the closest approximation, which
seldom is appropriate for the purposes of the Modus themes.
- In such a case, the user is expected to update their terminal's color
+ In such a case, the user is expected to update their terminal’s color
palette such as by adapting these resources (*note Preview theme
colors::):
@@ -2850,10 +2847,10 @@ selection process and just produces a preview for the
current Modus
theme.
When called with a prefix argument (‘C-u’ with the default key
-bindings), these commands will show a preview of the palette's semantic
-color mappings instead of the named colors. In this context, "named
-colors" are entries that associate a symbol to a string color value,
-such as ‘(blue-warmer "#354fcf")’. Whereas "semantic color mappings"
+bindings), these commands will show a preview of the palette’s semantic
+color mappings instead of the named colors. In this context, “named
+colors” are entries that associate a symbol to a string color value,
+such as ‘(blue-warmer "#354fcf")’. Whereas “semantic color mappings”
associate a named color to a symbol, like ‘(string blue-warmer)’, thus
making the theme render all string constructs in the ‘blue-warmer’ color
value (*note Option for palette overrides: Palette overrides.).
@@ -2935,7 +2932,7 @@ accounts for palette overrides. Else it reads only the
default palette.
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
+‘unspecified’ symbol, which is safe when used as a face attribute’s
value.
An example with ‘modus-operandi’ to show how this function behaves
@@ -3013,7 +3010,7 @@ File: modus-themes.info, Node: Do not extend the region
background, Next: Add
By the default, the background of the ‘region’ face extends from the end
of the line to the edge of the window. To limit it to the end of the
-line, we need to override the face's ‘:extend’ attribute. Adding this
+line, we need to override the face’s ‘:extend’ attribute. Adding this
to the Emacs configuration file will suffice:
;; Do not extend `region' background past the end of the line.
@@ -3029,10 +3026,10 @@ File: modus-themes.info, Node: Add padding to mode
line, Next: Remap face with
5.10 Add padding to mode line
=============================
-Emacs faces do not have a concept of "padding" for the space between the
+Emacs faces do not have a concept of “padding” for the space between the
text and its box boundaries. We can approximate the effect by adding a
‘:box’ attribute, making its border several pixels thick, and using the
-mode line's background color for it. This way the thick border will not
+mode line’s background color for it. This way the thick border will not
stand out and will appear as a continuation of the mode line.
*note Use theme colors in code with modus-themes-with-colors::.
@@ -3119,7 +3116,7 @@ code:
When ‘my-rainbow-region’ is called interactively, it prompts for a
color to use. The list of candidates is drawn from the car of each
-association in ‘my-rainbow-region-colors’ (so "red", "green", etc.).
+association in ‘my-rainbow-region-colors’ (so “red”, “green”, etc.).
To extend this principle, we may write wrapper functions that pass a
color directly. Those can be useful in tandem with hooks. Consider
@@ -3196,7 +3193,7 @@ value that is relative to the default, represented as a
floating point.
If you use an integer, then that means an absolute height. This is of
paramount importance: it ensures that all fonts can scale gracefully
when using something like the ‘text-scale-adjust’ command which only
-operates on the base font size (i.e. the ‘default’ face's absolute
+operates on the base font size (i.e. the ‘default’ face’s absolute
height).
*note Note for EWW and Elfeed fonts: Note on SHR fonts.
@@ -3308,7 +3305,7 @@ priority cookies to better match their workflow. User
options are
As those are meant to be custom faces, it is futile to have the
themes guess what each user wants to use, which keywords to target, and
so on. Instead, we can provide guidelines on how to customize things to
-one's liking with the intent of retaining the overall aesthetic of the
+one’s liking with the intent of retaining the overall aesthetic of the
themes.
Please bear in mind that the end result of those is not controlled by
@@ -3481,7 +3478,7 @@ text to, for example, a shade of red:
command ‘modus-themes-list-colors’ to show a buffer that previews each
entry in the palette.
- *note Visualize the active Modus theme's palette: Preview theme
+ *note Visualize the active Modus theme’s palette: Preview theme
colors.
Once we have defined the faces we need, we must update the
@@ -3496,7 +3493,7 @@ already styled by the themes, it probably is best not to
edit them:
("~" org-code verbatim)
("+" my-org-emphasis-strike-through)))
- That's it! For changes to take effect in already visited Org files,
+ That’s it! For changes to take effect in already visited Org files,
invoke ‘M-x org-mode-restart’.
@@ -3506,7 +3503,7 @@ File: modus-themes.info, Node: Update Org block
delimiter fontification, Next:
=============================================
As noted in the section about ‘modus-themes-org-blocks’, Org contains a
-variable that determines whether the block's begin and end lines are
+variable that determines whether the block’s begin and end lines are
extended to the edge of the window (*note Option for org-mode block
styles: Org mode blocks.). The variable is
‘org-fontify-whole-block-delimiter-line’.
@@ -3557,7 +3554,7 @@ colors.
accepts two color values and returns their contrast ratio. Values range
from 1 to 21 (lowest to highest). The themes are designed to always be
equal or higher than 7 for each combination of background and foreground
-that they use (this is the WCAG AAA standard--the most demanding of its
+that they use (this is the WCAG AAA standard—the most demanding of its
kind).
A couple of examples (rounded numbers):
@@ -3602,7 +3599,7 @@ in combination with some others. Consult the source code
for the
minutia and relevant commentary.
Such knowledge may prove valuable while attempting to customize the
-theme's color palette.
+theme’s color palette.
File: modus-themes.info, Node: Load theme depending on time of day, Next:
Backdrop for pdf-tools, Prev: Measure color contrast, Up: Advanced
customization
@@ -3614,7 +3611,7 @@ While we do provide ‘modus-themes-toggle’ to manually
switch between the
themes, users may also set up their system to perform such a task
automatically at sunrise and sunset.
- This can be accomplished by specifying the coordinates of one's
+ This can be accomplished by specifying the coordinates of one’s
location using the built-in ‘solar.el’ and then configuring the
‘circadian’ package:
@@ -3638,9 +3635,9 @@ File: modus-themes.info, Node: Backdrop for pdf-tools,
Next: Toggle themes wit
===========================
Most PDF files use a white background for their page, making it
-impossible to discern the file's boundaries in the buffer while using
+impossible to discern the file’s boundaries in the buffer while using
the Modus Operandi theme. To introduce a distinction between the
-buffer's backdrop and the PDF page's background, the former must be
+buffer’s backdrop and the PDF page’s background, the former must be
rendered as some shade of gray. Ideally, ‘pdf-tools’ would provide a
face that the themes could support directly, though this does not seem
to be the case for the time being. We must thus employ the face
@@ -3649,7 +3646,7 @@ change the buffer-local value of the ‘default’ face.
*note Remap face with local value::.
- To remap the buffer's backdrop, we start with a function like this
+ To remap the buffer’s backdrop, we start with a function like this
one:
(defun my-pdf-tools-backdrop ()
@@ -3804,11 +3801,11 @@ window.
windows.
2. Make the relevant faces invisible by changing the value of their
- relevant attributes to that of the current theme's main background.
+ relevant attributes to that of the current theme’s main background.
The parameters of Emacs frames are specified in the variables
-‘initial-frame-alist’ and ‘default-frame-alist’. The "initial frame"
-refers to the first frame that appears on Emacs startup. The "default"
+‘initial-frame-alist’ and ‘default-frame-alist’. The “initial frame”
+refers to the first frame that appears on Emacs startup. The “default”
refers to the fallback values that apply to all other frames that Emacs
creates (unless those are explicitly overridden by a bespoke
‘make-frame’ call).
@@ -3826,8 +3823,8 @@ variables:
we specify there. This economizes on typing.
Then we define a function that makes the relevant faces invisible.
-The reason we do this with a function is so we can hook it to the "post
-load" phase of a theme, thus applying the new background value
+The reason we do this with a function is so we can hook it to the “post
+load” phase of a theme, thus applying the new background value
(otherwise you keep the old background, which likely means that the
faces will no longer be invisible).
@@ -3845,9 +3842,9 @@ faces will no longer be invisible).
The above will work only for themes that belong to the Modus family.
For users of Emacs version 29 or higher, there exists a theme-agnostic
-hook that takes a function with one argument--that of the theme--and
-calls in the the "post enable" phase of theme loading. Here is the
-above snippet, with the necessary tweaks:
+hook that takes a function with one argument—that of the theme—and calls
+in the the “post enable” phase of theme loading. Here is the above
+snippet, with the necessary tweaks:
(defun my-modus-themes-invisible-dividers (_theme)
"Make window dividers for THEME invisible."
@@ -3906,7 +3903,7 @@ File: modus-themes.info, Node: Add support for
solaire-mode, Prev: Custom hl-t
=================================
The ‘solaire-mode’ package dims the background of what it considers
-ancillary "UI" buffers, such as the minibuffer and Dired buffers. The
+ancillary “UI” buffers, such as the minibuffer and Dired buffers. The
Modus themes used to support Solaire on the premise that the user was
(i) opting in to it, (ii) understood why certain buffers were more gray,
and (iii) knew what other adjustments had to be made to prevent broken
@@ -3929,16 +3926,16 @@ sort are unsustainable and penalize the entire
userbase. Besides, the
themes are built into Emacs and we must keep their standard high.
The fundamental constraint with Solaire is that Emacs does not have a
-real distinction between "content" and "UI" buffers. For themes to work
+real distinction between “content” and “UI” buffers. For themes to work
with Solaire, they need to be designed around that package. Such is an
arrangement that compromises on our accessibility standards and/or
hinders our efforts to provide the best possible experience while using
the Modus themes.
- As such, ‘solaire-mode’ is not--and will not be--supported by the
-Modus themes (or any other of my themes, for that matter). Users who
-want it must style the faces manually. Below is some sample code, based
-on what we cover at length elsewhere in this manual:
+ As such, ‘solaire-mode’ is not—and will not be—supported by the Modus
+themes (or any other of my themes, for that matter). Users who want it
+must style the faces manually. Below is some sample code, based on what
+we cover at length elsewhere in this manual:
*note Advanced customization::.
@@ -3980,7 +3977,7 @@ File: modus-themes.info, Node: Supported packages,
Next: Indirectly covered pa
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. The items with an appended asterisk ‘*’ tend to
-have lots of extensions, so the "full support" may not be 100% true…
+have lots of extensions, so the “full support” may not be 100% true…
• ace-window
• agda2-mode
@@ -4206,7 +4203,7 @@ have lots of extensions, so the "full support" may not be
100% true…
• terraform-mode
• term
• textsec
- • transient (pop-up windows such as Magit's)
+ • transient (pop-up windows such as Magit’s)
• trashed
• tree-sitter
• tty-menu
@@ -4509,7 +4506,7 @@ File: modus-themes.info, Node: Note on
display-fill-column-indicator-mode, Nex
The ‘display-fill-column-indicator-mode’ uses a typographic character to
draw its line. This has the downside of creating a dashed line. The
-dashes are further apart depending on how tall the font's glyph height
+dashes are further apart depending on how tall the font’s glyph height
is and what integer the ‘line-spacing’ is set to.
At the theme level we eliminate this effect by making the character
@@ -4545,7 +4542,7 @@ their own by configuring certain variables.
To make the Modus themes work as expected with this, we need to use
some of the techniques that are discussed at length in the various
-"Do-It-Yourself" (DIY) sections, which provide insight into the more
+“Do-It-Yourself” (DIY) sections, which provide insight into the more
advanced customization options of the themes.
*note Advanced customization::.
@@ -4668,7 +4665,7 @@ is that they must not interfere with existing
fontification. Those
background colors need to be distinct from each other, such as an
unambiguous red juxtaposed with a clear blue.
- While this design may be internally consistent with the raison d'être
+ While this design may be internally consistent with the raison d’être
of that library, it inevitably produces inaccessible color combinations.
There are two competing goals at play:
@@ -4711,7 +4708,7 @@ File: modus-themes.info, Node: Note for prism, Next:
Note on company-mode over
7.10 Note on prism.el
=====================
-This package by Adam Porter, aka "alphapapa" or "github-alphapapa",
+This package by Adam Porter, aka “alphapapa” or “github-alphapapa”,
implements an alternative to the typical coloration of code. Instead of
highlighting the syntactic constructs, it applies color to different
levels of depth in the code structure.
@@ -4768,7 +4765,7 @@ modus-themes-with-colors::.
cyan)))
And this is with 4 colors, which produces results that are the
-closest to the themes' default aesthetic:
+closest to the themes’ default aesthetic:
(setq prism-num-faces 4)
@@ -4805,7 +4802,7 @@ is drawn using an overlay. This creates alignment issues
every time it
is placed above a piece of text that has a different height than the
default.
- The solution recommended by the project's maintainer is to use an
+ The solution recommended by the project’s maintainer is to use an
alternative front-end for drawing the pop-up which draws child frames
instead of overlays.(1)(2)
@@ -4871,8 +4868,8 @@ File: modus-themes.info, Node: Note on SHR colors,
Next: Note on SHR fonts, P
7.14 Note on SHR colors
=======================
-Emacs' HTML rendering library (‘shr.el’) may need explicit configuration
-to respect the theme's colors instead of whatever specifications the
+Emacs’ HTML rendering library (‘shr.el’) may need explicit configuration
+to respect the theme’s colors instead of whatever specifications the
webpage provides.
Consult the doc string of ‘shr-use-colors’.
@@ -4904,7 +4901,7 @@ File: modus-themes.info, Node: Note on Ement colors and
fonts, Next: Note on p
7.16 Note on Ement colors and fonts
===================================
-The ‘ement.el’ library by Adam Porter (also known as "alphapapa")
+The ‘ement.el’ library by Adam Porter (also known as “alphapapa”)
defaults to a method of colorizing usernames in a rainbow style. This
is controlled by the user option ‘ement-room-prism’ and can be disabled
with:
@@ -4920,7 +4917,7 @@ which is slightly below our nominal target. Try this
instead:
With regard to fonts, Ement depends on ‘shr’ (*note Note on SHR
fonts::).
- Since we are here, here is an excerpt from Ement's source code:
+ Since we are here, here is an excerpt from Ement’s source code:
(defcustom ement-room-prism-minimum-contrast 6
"Attempt to enforce this minimum contrast ratio for user faces.
@@ -4941,12 +4938,12 @@ File: modus-themes.info, Node: Note on pdf-tools link
hints, Next: Note on the
=================================
Hints are drawn by ImageMagick (https://imagemagick.org/), not Emacs,
-i.e., ImageMagick doesn't know about the hint face unless you tell
+i.e., ImageMagick doesn’t know about the hint face unless you tell
ImageMagick about it. By default, only the foreground and background
color attributes are passed. The below snippet adds to those the
various font attributes. As it queries various faces, specifically
‘pdf-links-read-link’ and the faces it inherits, it needs to be added to
-your initialization file after you've customized any faces.
+your initialization file after you’ve customized any faces.
(use-package pdf-links
:config
@@ -4989,8 +4986,8 @@ File: modus-themes.info, Node: Note on the Notmuch logo,
Next: Note on goto-ad
7.18 Note on the Notmuch logo
=============================
-By default, the "hello" buffer of Notmuch includes a header with the
-programs' logo and a couple of buttons. The logo has the effect of
+By default, the “hello” buffer of Notmuch includes a header with the
+programs’ logo and a couple of buttons. The logo has the effect of
enlarging the height of the line, which negatively impacts the shape of
those buttons. Disabling the logo fixes the problem:
@@ -5028,7 +5025,7 @@ File: modus-themes.info, Node: Frequently Asked
Questions, Next: Contributing,
****************************
In this section we provide answers related to some aspects of the Modus
-themes' design and application.
+themes’ design and application.
* Menu:
@@ -5078,7 +5075,7 @@ looks do not overdo it with the application of color.
*note Customization Options: Customization options.
- This is the non-quantifiable aspect of the themes' design: the
+ This is the non-quantifiable aspect of the themes’ design: the
artistic part, if you will. There are a lot of cases where color can be
used inconsiderately, without accounting for layout, typographic, or
other properties of the presentation. For example, two headings with
@@ -5207,16 +5204,16 @@ direct sunlight or has plenty of light. Whereas
‘modus-vivendi’ works
better when there is not a lot of sunshine or the room has a source of
light that is preferably a faint and/or warm one. It is possible to use
‘modus-operandi’ at night and ‘modus-vivendi’ during the day, though
-that will depend on several variables, such as one's overall perception
+that will depend on several variables, such as one’s overall perception
of color, the paint on the walls and how that contributes to the
-impression of lightness in the room, the sense of space within the eye's
+impression of lightness in the room, the sense of space within the eye’s
peripheral vision, hardware specifications, and environmental factors.
In general, an additional source of light other than that of the
monitor can help reduce eye strain: the eyes are more relaxed when they
do not have to focus on one point to gather light.
- The monitor's display settings must be accounted for. Gamma values,
+ The monitor’s display settings must be accounted for. Gamma values,
in particular, need to be calibrated to neither amplify nor distort the
perception of black. Same principle for sharpness, brightness, and
contrast as determined by the hardware, which all have an effect on how
@@ -5256,19 +5253,19 @@ uniformity.
In practical terms, a color scheme is what one uses when, for
example, they replace the first sixteen escape sequences of a terminal
emulator with color values of their preference. The terminal offers the
-option to choose, say, the exact value of what counts as "red", but does
+option to choose, say, the exact value of what counts as “red”, but does
not provide the means to control where that is mapped to and whether it
should also have other qualities such as a bold weight for the
underlying text or an added background color. In contradistinction,
-Emacs uses constructs known as "faces" which allow the user/developer to
+Emacs uses constructs known as “faces” which allow the user/developer to
specify where a given color will be used and whether it should be
accompanied by other typographic or stylistic attributes.
By configuring the multitude of faces on offer we thus control both
which colors are applied and how they appear in their context. When a
-package wants to render each instance of "foo" with the "bar" face, it
+package wants to render each instance of “foo” with the “bar” face, it
is not requesting a specific color, which makes things considerably more
-flexible as we can treat "bar" in its own right without necessarily
+flexible as we can treat “bar” in its own right without necessarily
having to use some color value that we hardcoded somewhere.
Which brings us to the distinction between consistency and uniformity
@@ -5282,7 +5279,7 @@ to view its contents and (ii) underlining everything
would make the
interface virtually unusable.
Again, one must exercise judgement in order to avoid discrimination,
-where "discrimination" refers to:
+where “discrimination” refers to:
• The treatment of substantially different magnitudes as if they were
of the same class.
@@ -5293,11 +5290,11 @@ where "discrimination" refers to:
alike.)
If, in other words, one is to enforce uniformity without accounting
-for the particular requirements of each case--the contextual demands for
-usability beyond matters of color--they are making a not-so-obvious
-error of treating different cases as if they were the same.
+for the particular requirements of each case—the contextual demands for
+usability beyond matters of color—they are making a not-so-obvious error
+of treating different cases as if they were the same.
- The Modus themes prioritize "thematic consistency" over abstract
+ The Modus themes prioritize “thematic consistency” over abstract
harmony or regularity among their applicable colors. In concrete terms,
we do not claim that, say, our yellows are the best complements for our
blues because we generally avoid using complementary colors
@@ -5325,8 +5322,8 @@ daily basis.
template, doing so would run contrary to how this project is maintained
where details matter greatly.
- Each program has its own requirements so it won't always be
-possible--or indeed desirable--to have 1:1 correspondence between what
+ Each program has its own requirements so it won’t always be
+possible—or indeed desirable—to have 1:1 correspondence between what
applies to Emacs and what should be done elsewhere. No port should ever
strive to be a copy of the Emacs implementation, as no other program is
an Emacs equivalent, but instead try to follow the spirit of the design.
@@ -5348,12 +5345,12 @@ the needs of users with red-green/blue-yellow color
deficiency
paradigms and/or by providing yellow+blue variants for deuteranopia and
red+cyan for tritanopia (*note Overview::).
- The latter criterion is the "je ne sais quoi" of the artistic aspect
+ The latter criterion is the “je ne sais quoi” of the artistic aspect
of the themes, which is partially fleshed out in this manual.
*note Frequently Asked Questions::.
- With regard to the artistic aspect (where "art" qua skill may amount
+ With regard to the artistic aspect (where “art” qua skill may amount
to an imprecise science), there is no hard-and-fast rule in effect as it
requires one to exercize discretion and make decisions based on
context-dependent information or constraints. As is true with most
@@ -5422,7 +5419,7 @@ modus-themes public mailing list
• Suggest refinements to the color palette.
• Help expand this document or any other piece of documentation.
• Send patches for code refinements (if you need, ask me for help
- with Git--we all start out as beginners).
+ with Git—we all start out as beginners).
*note Patches require copyright assignment to the FSF::.
@@ -5536,7 +5533,7 @@ Ideas and user feedback
Gustavo Barros, Hörmetjan Yiltiz, Ilja Kocken, Imran Khan, Iris
Garcia, Ivan Popovych, James Ferguson, Jeremy Friesen, Jerry Zhang,
Johannes Grødem, John Haman, John Wick, Jonas Collberg, Jorge
- Morais, Joshua O'Connor, Julio C. Villasante, Kenta Usami, Kevin
+ Morais, Joshua O’Connor, Julio C. Villasante, Kenta Usami, Kevin
Fleming, Kévin Le Gouguec, Kevin Kainan Li, Kostadin Ninev, Laith
Bahodi, Lasse Lindner, Len Trigg, Lennart C. Karssen, Luis Miguel
Castañeda, Magne Hov, Manuel Giraud, Manuel Uberti, Mark Bestley,
@@ -5570,7 +5567,7 @@ Inspiration for certain features
Special thanks (from A-Z) to Daniel Mendler, Gustavo Barros, Manuel
Uberti, Nicolas De Jaeghere, and Omar Antolín Camarena for their long
time contributions and insightful commentary on key aspects of the
-themes' design and/or aspects of their functionality.
+themes’ design and/or aspects of their functionality.
All errors are my own.
@@ -5598,7 +5595,7 @@ Appendix A GNU Free Documentation License
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
- This License is a kind of "copyleft", which means that derivative
+ This License is a kind of “copyleft”, which means that derivative
works of the document must themselves be free in the same sense.
It complements the GNU General Public License, which is a copyleft
license designed for free software.
@@ -5619,18 +5616,18 @@ Appendix A GNU Free Documentation License
be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
- "Document", below, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You accept
+ “Document”, below, refers to any such manual or work. Any member
+ of the public is a licensee, and is addressed as “you”. You accept
the license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
- A "Modified Version" of the Document means any work containing the
+ A “Modified Version” of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
- A "Secondary Section" is a named appendix or a front-matter section
+ A “Secondary Section” is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall
+ publishers or authors of the Document to the Document’s overall
subject (or to related matters) and contains nothing that could
fall directly within that overall subject. (Thus, if the Document
is in part a textbook of mathematics, a Secondary Section may not
@@ -5639,7 +5636,7 @@ Appendix A GNU Free Documentation License
of legal, commercial, philosophical, ethical or political position
regarding them.
- The "Invariant Sections" are certain Secondary Sections whose
+ The “Invariant Sections” are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in the
notice that says that the Document is released under this License.
If a section does not fit the above definition of Secondary then it
@@ -5647,13 +5644,13 @@ Appendix A GNU Free Documentation License
contain zero Invariant Sections. If the Document does not identify
any Invariant Sections then there are none.
- The "Cover Texts" are certain short passages of text that are
+ The “Cover Texts” are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License. A
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
- A "Transparent" copy of the Document means a machine-readable copy,
+ A “Transparent” copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed
@@ -5665,7 +5662,7 @@ Appendix A GNU Free Documentation License
been arranged to thwart or discourage subsequent modification by
readers is not Transparent. An image format is not Transparent if
used for any substantial amount of text. A copy that is not
- "Transparent" is called "Opaque".
+ “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
@@ -5678,23 +5675,23 @@ Appendix A GNU Free Documentation License
the machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.
- The "Title Page" means, for a printed book, the title page itself,
+ The “Title Page” means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
material this License requires to appear in the title page. For
- works in formats which do not have any title page as such, "Title
- Page" means the text near the most prominent appearance of the
- work's title, preceding the beginning of the body of the text.
+ works in formats which do not have any title page as such, “Title
+ Page” means the text near the most prominent appearance of the
+ work’s title, preceding the beginning of the body of the text.
- The "publisher" means any person or entity that distributes copies
+ The “publisher” means any person or entity that distributes copies
of the Document to the public.
- A section "Entitled XYZ" means a named subunit of the Document
+ A section “Entitled XYZ” means a named subunit of the Document
whose title either is precisely XYZ or contains XYZ in parentheses
following text that translates XYZ in another language. (Here XYZ
stands for a specific section name mentioned below, such as
- "Acknowledgements", "Dedications", "Endorsements", or "History".)
- To "Preserve the Title" of such a section when you modify the
- Document means that it remains a section "Entitled XYZ" according
+ “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.)
+ To “Preserve the Title” of such a section when you modify the
+ Document means that it remains a section “Entitled XYZ” according
to this definition.
The Document may include Warranty Disclaimers next to the notice
@@ -5724,7 +5721,7 @@ Appendix A GNU Free Documentation License
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100, and
- the Document's license notice requires Cover Texts, you must
+ the Document’s license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
@@ -5796,15 +5793,15 @@ Appendix A GNU Free Documentation License
the Addendum below.
G. Preserve in that license notice the full lists of Invariant
- Sections and required Cover Texts given in the Document's
+ Sections and required Cover Texts given in the Document’s
license notice.
H. Include an unaltered copy of this License.
- I. Preserve the section Entitled "History", Preserve its Title,
+ I. Preserve the section Entitled “History”, Preserve its Title,
and add to it an item stating at least the title, year, new
authors, and publisher of the Modified Version as given on the
- Title Page. If there is no section Entitled "History" in the
+ Title Page. If there is no section Entitled “History” in the
Document, create one stating the title, year, authors, and
publisher of the Document as given on its Title Page, then add
an item describing the Modified Version as stated in the
@@ -5814,12 +5811,12 @@ Appendix A GNU Free Documentation License
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in the
- "History" section. You may omit a network location for a work
+ “History” section. You may omit a network location for a work
that was published at least four years before the Document
itself, or if the original publisher of the version it refers
to gives permission.
- K. For any section Entitled "Acknowledgements" or "Dedications",
+ K. For any section Entitled “Acknowledgements” or “Dedications”,
Preserve the Title of the section, and preserve in the section
all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
@@ -5828,11 +5825,11 @@ Appendix A GNU Free Documentation License
in their text and in their titles. Section numbers or the
equivalent are not considered part of the section titles.
- M. Delete any section Entitled "Endorsements". Such a section
+ M. Delete any section Entitled “Endorsements”. Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled
- "Endorsements" or to conflict in title with any Invariant
+ “Endorsements” or to conflict in title with any Invariant
Section.
O. Preserve any Warranty Disclaimers.
@@ -5841,15 +5838,15 @@ Appendix A GNU Free Documentation License
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option designate
some or all of these sections as invariant. To do this, add their
- titles to the list of Invariant Sections in the Modified Version's
+ titles to the list of Invariant Sections in the Modified Version’s
license notice. These titles must be distinct from any other
section titles.
- You may add a section Entitled "Endorsements", provided it contains
+ You may add a section Entitled “Endorsements”, provided it contains
nothing but endorsements of your Modified Version by various
- parties--for example, statements of peer review or that the text
- has been approved by an organization as the authoritative
- definition of a standard.
+ parties—for example, statements of peer review or that the text has
+ been approved by an organization as the authoritative definition of
+ a standard.
You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end of
@@ -5887,10 +5884,10 @@ Appendix A GNU Free Documentation License
combined work.
In the combination, you must combine any sections Entitled
- "History" in the various original documents, forming one section
- Entitled "History"; likewise combine any sections Entitled
- "Acknowledgements", and any sections Entitled "Dedications". You
- must delete all sections Entitled "Endorsements."
+ “History” in the various original documents, forming one section
+ Entitled “History”; likewise combine any sections Entitled
+ “Acknowledgements”, and any sections Entitled “Dedications”. You
+ must delete all sections Entitled “Endorsements.”
6. COLLECTIONS OF DOCUMENTS
@@ -5911,16 +5908,16 @@ Appendix A GNU Free Documentation License
A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of a
- storage or distribution medium, is called an "aggregate" if the
+ storage or distribution medium, is called an “aggregate” if the
copyright resulting from the compilation is not used to limit the
- legal rights of the compilation's users beyond what the individual
+ legal rights of the compilation’s users beyond what the individual
works permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate which
are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half
- of the entire aggregate, the Document's Cover Texts may be placed
+ of the entire aggregate, the Document’s Cover Texts may be placed
on covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic
form. Otherwise they must appear on printed covers that bracket
@@ -5942,8 +5939,8 @@ Appendix A GNU Free Documentation License
this License or a notice or disclaimer, the original version will
prevail.
- If a section in the Document is Entitled "Acknowledgements",
- "Dedications", or "History", the requirement (section 4) to
+ If a section in the Document is Entitled “Acknowledgements”,
+ “Dedications”, or “History”, the requirement (section 4) to
Preserve its Title (section 1) will typically require changing the
actual title.
@@ -5984,7 +5981,7 @@ Appendix A GNU Free Documentation License
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
- version of this License "or any later version" applies to it, you
+ version of this License “or any later version” applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation. If the
@@ -5992,29 +5989,29 @@ Appendix A GNU Free Documentation License
choose any version ever published (not as a draft) by the Free
Software Foundation. If the Document specifies that a proxy can
decide which future versions of this License can be used, that
- proxy's public statement of acceptance of a version permanently
+ proxy’s public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
11. RELICENSING
- "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
+ “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server.
- A "Massive Multiauthor Collaboration" (or "MMC") contained in the
+ A “Massive Multiauthor Collaboration” (or “MMC”) contained in the
site means any set of copyrightable works thus published on the MMC
site.
- "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
+ “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
- "Incorporate" means to publish or republish a Document, in whole or
+ “Incorporate” means to publish or republish a Document, in whole or
in part, as part of another Document.
- An MMC is "eligible for relicensing" if it is licensed under this
+ An MMC is “eligible for relicensing” if it is licensed under this
License, and if all works that were first published under this
License somewhere other than this MMC, and subsequently
incorporated in whole or in part into the MMC, (1) had no cover
@@ -6041,7 +6038,7 @@ notices just after the title page:
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -6209,126 +6206,126 @@ B.3 Concept index
Tag Table:
Node: Top872
-Node: Overview8163
-Node: How do the themes look like10929
-Node: Learn about the latest changes11288
-Node: Installation11676
-Node: Install manually from source12602
-Node: Install from the archives13425
-Node: Install on GNU/Linux14024
-Node: Debian 11 Bullseye14515
-Node: GNU Guix14923
-Node: Dealing with byte compilation errors15206
-Node: Enable and load16364
-Node: The require-theme for built-in Emacs themes20308
-Node: Sample configuration with and without use-package21428
-Node: Differences between loading and enabling24337
-Node: Customization options26367
-Node: Custom reload theme30153
-Node: Disable other themes31073
-Node: Bold constructs32315
-Node: Italic constructs33152
-Node: Option for which themes to toggle33945
-Node: Mixed fonts34720
-Node: Command prompts35732
-Node: Completion UIs37535
-Node: Org mode blocks40335
-Node: Heading styles42230
-Node: UI typeface46582
-Node: Palette overrides47513
-Node: Advanced customization51844
-Node: Palette override presets53499
-Node: Stylistic variants using palette overrides56283
-Node: Make the mode line borderless58195
-Node: Make the active mode line colorful59797
-Node: Make the tab bar more or less colorful61742
-Node: Make the fringe invisible or another color63973
-Node: Make links use subtle or no underlines65463
-Node: Make prompts more or less colorful66460
-Node: Make completion matches more or less colorful68124
-Node: Make comments yellow and strings green72024
-Node: Make code syntax use the old alt-syntax style73925
-Node: Make use of alternative styles for code syntax77196
-Node: Make matching parenthesis more or less intense80860
-Node: Make box buttons more or less gray82296
-Node: Make TODO and DONE more or less intense83602
-Node: Make headings more or less colorful85305
-Node: Make Org agenda more or less colorful87705
-Node: Make inline code in prose use alternative styles91165
-Node: Make mail citations and headers more or less colorful93704
-Node: Make the region preserve text colors plus other styles96399
-Node: Make mouse highlights more or less colorful98210
-Node: Make language underlines less colorful99517
-Node: Make line numbers use alternative styles100963
-Node: Make diffs use only a foreground102900
-Node: Make deuteranopia diffs red and blue instead of yellow and blue105666
-Node: Make the themes look like what the maintainer uses108080
-Node: More accurate colors in terminal emulators112778
-Node: Range of color with terminal emulators114066
-Node: Preview theme colors116774
-Node: Per-theme customization settings118609
-Node: Get a single color from the palette119955
-Node: Use theme colors in code with modus-themes-with-colors122201
-Node: Do not extend the region background124534
-Node: Add padding to mode line125330
-Node: Remap face with local value127888
-Node: Font configurations for Org and others130303
-Ref: Font configurations for Org and others-Footnote-1133210
-Node: Configure bold and italic faces133397
-Node: Custom Org todo keyword and priority faces137580
-Node: Custom Org emphasis faces141297
-Node: Update Org block delimiter fontification146116
-Node: Measure color contrast148031
-Node: Load theme depending on time of day150726
-Node: Backdrop for pdf-tools151734
-Node: Toggle themes without reloading them154669
-Node: A theme-agnostic hook for theme loading155945
-Node: Use more spacious margins or padding in Emacs frames158398
-Node: Custom hl-todo colors162468
-Node: Add support for solaire-mode164006
-Node: Face coverage166903
-Node: Supported packages167355
-Node: Indirectly covered packages172983
-Node: Notes on individual packages174352
-Node: Note on calendarel weekday and weekend colors175452
-Node: Note on git-gutter in Doom Emacs176600
-Node: Note on php-mode multiline comments178941
-Node: Note on underlines in compilation buffers179694
-Node: Note on inline Latex in Org buffers180531
-Node: Note on dimmerel181141
-Node: Note on display-fill-column-indicator-mode182626
-Node: Note on highlight-parenthesesel184023
-Node: Note on mmm-modeel background colors189997
-Node: Note for prism192295
-Node: Note on company-mode overlay pop-up195453
-Ref: Note on company-mode overlay pop-up-Footnote-1196181
-Ref: Note on company-mode overlay pop-up-Footnote-2196248
-Node: Note on ERC escaped color sequences196303
-Ref: Note on ERC escaped color sequences-Footnote-1197731
-Node: Note on powerline or spaceline197841
-Node: Note on SHR colors198255
-Node: Note on SHR fonts198675
-Node: Note on Ement colors and fonts199320
-Node: Note on pdf-tools link hints200824
-Node: Note on the Notmuch logo203280
-Node: Note on goto-address-mode faces203812
-Node: Frequently Asked Questions204930
-Node: Is the contrast ratio about adjacent colors?205559
-Node: What does it mean to avoid exaggerations?207066
-Node: Why are colors mostly variants of blue magenta cyan?208914
-Node: What is the best setup for legibility?213220
-Node: Are these color schemes?215859
-Node: Port the Modus themes to other platforms?219511
-Node: Contributing222343
-Node: Sources of the themes222740
-Node: Issues you can help with223634
-Node: Patches require copyright assignment to the FSF225024
-Node: Acknowledgements227244
-Node: GNU Free Documentation License231411
-Node: Indices256574
-Node: Function index256753
-Node: Variable index258009
-Node: Concept index260687
+Node: Overview8011
+Node: How do the themes look like10783
+Node: Learn about the latest changes11142
+Node: Installation11530
+Node: Install manually from source12460
+Node: Install from the archives13285
+Node: Install on GNU/Linux13884
+Node: Debian 11 Bullseye14377
+Node: GNU Guix14787
+Node: Dealing with byte compilation errors15070
+Node: Enable and load16228
+Node: The require-theme for built-in Emacs themes20172
+Node: Sample configuration with and without use-package21292
+Node: Differences between loading and enabling24203
+Node: Customization options26241
+Node: Custom reload theme30027
+Node: Disable other themes30947
+Node: Bold constructs32189
+Node: Italic constructs33026
+Node: Option for which themes to toggle33819
+Node: Mixed fonts34594
+Node: Command prompts35606
+Node: Completion UIs37411
+Node: Org mode blocks40213
+Node: Heading styles42118
+Node: UI typeface46474
+Node: Palette overrides47405
+Node: Advanced customization51740
+Node: Palette override presets53403
+Node: Stylistic variants using palette overrides56195
+Node: Make the mode line borderless58107
+Node: Make the active mode line colorful59709
+Node: Make the tab bar more or less colorful61654
+Node: Make the fringe invisible or another color63885
+Node: Make links use subtle or no underlines65379
+Node: Make prompts more or less colorful66376
+Node: Make completion matches more or less colorful68040
+Node: Make comments yellow and strings green71940
+Node: Make code syntax use the old alt-syntax style73843
+Node: Make use of alternative styles for code syntax77124
+Node: Make matching parenthesis more or less intense80788
+Node: Make box buttons more or less gray82224
+Node: Make TODO and DONE more or less intense83530
+Node: Make headings more or less colorful85233
+Node: Make Org agenda more or less colorful87633
+Node: Make inline code in prose use alternative styles91093
+Node: Make mail citations and headers more or less colorful93634
+Node: Make the region preserve text colors plus other styles96329
+Node: Make mouse highlights more or less colorful98140
+Node: Make language underlines less colorful99447
+Node: Make line numbers use alternative styles100893
+Node: Make diffs use only a foreground102830
+Node: Make deuteranopia diffs red and blue instead of yellow and blue105600
+Node: Make the themes look like what the maintainer uses108022
+Node: More accurate colors in terminal emulators112720
+Node: Range of color with terminal emulators114012
+Node: Preview theme colors116726
+Node: Per-theme customization settings118571
+Node: Get a single color from the palette119917
+Node: Use theme colors in code with modus-themes-with-colors122165
+Node: Do not extend the region background124498
+Node: Add padding to mode line125296
+Node: Remap face with local value127860
+Node: Font configurations for Org and others130283
+Ref: Font configurations for Org and others-Footnote-1133192
+Node: Configure bold and italic faces133379
+Node: Custom Org todo keyword and priority faces137562
+Node: Custom Org emphasis faces141281
+Node: Update Org block delimiter fontification146104
+Node: Measure color contrast148021
+Node: Load theme depending on time of day150719
+Node: Backdrop for pdf-tools151729
+Node: Toggle themes without reloading them154672
+Node: A theme-agnostic hook for theme loading155948
+Node: Use more spacious margins or padding in Emacs frames158401
+Node: Custom hl-todo colors162491
+Node: Add support for solaire-mode164029
+Node: Face coverage166940
+Node: Supported packages167392
+Node: Indirectly covered packages173026
+Node: Notes on individual packages174395
+Node: Note on calendarel weekday and weekend colors175495
+Node: Note on git-gutter in Doom Emacs176643
+Node: Note on php-mode multiline comments178984
+Node: Note on underlines in compilation buffers179737
+Node: Note on inline Latex in Org buffers180574
+Node: Note on dimmerel181184
+Node: Note on display-fill-column-indicator-mode182669
+Node: Note on highlight-parenthesesel184068
+Node: Note on mmm-modeel background colors190046
+Node: Note for prism192346
+Node: Note on company-mode overlay pop-up195514
+Ref: Note on company-mode overlay pop-up-Footnote-1196244
+Ref: Note on company-mode overlay pop-up-Footnote-2196311
+Node: Note on ERC escaped color sequences196366
+Ref: Note on ERC escaped color sequences-Footnote-1197794
+Node: Note on powerline or spaceline197904
+Node: Note on SHR colors198318
+Node: Note on SHR fonts198742
+Node: Note on Ement colors and fonts199387
+Node: Note on pdf-tools link hints200897
+Node: Note on the Notmuch logo203357
+Node: Note on goto-address-mode faces203895
+Node: Frequently Asked Questions205013
+Node: Is the contrast ratio about adjacent colors?205644
+Node: What does it mean to avoid exaggerations?207151
+Node: Why are colors mostly variants of blue magenta cyan?209001
+Node: What is the best setup for legibility?213307
+Node: Are these color schemes?215952
+Node: Port the Modus themes to other platforms?219634
+Node: Contributing222478
+Node: Sources of the themes222875
+Node: Issues you can help with223769
+Node: Patches require copyright assignment to the FSF225160
+Node: Acknowledgements227380
+Node: GNU Free Documentation License231551
+Node: Indices256915
+Node: Function index257094
+Node: Variable index258350
+Node: Concept index261028
End Tag Table
diff --git a/doc/modus-themes.org b/doc/modus-themes.org
index 2c29b3ced9..f35d9d9202 100644
--- a/doc/modus-themes.org
+++ b/doc/modus-themes.org
@@ -35,14 +35,12 @@ Current development target is {{{development-version}}}.
+ Package name (GNU ELPA): ~modus-themes~
+ Official manual: <https://protesilaos.com/emacs/modus-themes>
+ Change log: <https://protesilaos.com/emacs/modus-themes-changelog>
-+ Color palette: <https://protesilaos.com/emacs/modus-themes-colors>
++ Colour palette: <https://protesilaos.com/emacs/modus-themes-colors>
+ Sample pictures: <https://protesilaos.com/emacs/modus-themes-pictures>
-+ Git repo on SourceHut: <https://git.sr.ht/~protesilaos/modus-themes>
- - Mirrors:
- + GitHub: <https://github.com/protesilaos/modus-themes>
- + GitLab: <https://gitlab.com/protesilaos/modus-themes>
-+ Mailing list: <https://lists.sr.ht/~protesilaos/modus-themes>
-+ Backronym: My Old Display Unexpectedly Sharpened ... themes
++ Git repositories:
+ + GitHub: <https://github.com/protesilaos/modus-themes>
+ + GitLab: <https://gitlab.com/protesilaos/modus-themes>
++ Backronym: My Old Display Unexpectedly Sharpened ... themes.
#+toc: headlines 8 insert TOC here, with eight headline levels
diff --git a/modus-operandi-deuteranopia-theme.el
b/modus-operandi-deuteranopia-theme.el
index a343f42ac2..29ae7e0c1f 100644
--- a/modus-operandi-deuteranopia-theme.el
+++ b/modus-operandi-deuteranopia-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-operandi-theme.el b/modus-operandi-theme.el
index 1509fd1297..f6eaba05f1 100644
--- a/modus-operandi-theme.el
+++ b/modus-operandi-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-operandi-tinted-theme.el b/modus-operandi-tinted-theme.el
index c395dc3c7d..deda4db710 100644
--- a/modus-operandi-tinted-theme.el
+++ b/modus-operandi-tinted-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-operandi-tritanopia-theme.el
b/modus-operandi-tritanopia-theme.el
index b2e208bff5..705172f96c 100644
--- a/modus-operandi-tritanopia-theme.el
+++ b/modus-operandi-tritanopia-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-themes.el b/modus-themes.el
index 57a676ee91..e4e009ca53 100644
--- a/modus-themes.el
+++ b/modus-themes.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Version: 4.3.0
;; Package-Requires: ((emacs "27.1"))
;; Keywords: faces, theme, accessibility
diff --git a/modus-vivendi-deuteranopia-theme.el
b/modus-vivendi-deuteranopia-theme.el
index 7cd9c679c0..6219185bea 100644
--- a/modus-vivendi-deuteranopia-theme.el
+++ b/modus-vivendi-deuteranopia-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-vivendi-theme.el b/modus-vivendi-theme.el
index 67e5b38774..057a7fef9c 100644
--- a/modus-vivendi-theme.el
+++ b/modus-vivendi-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-vivendi-tinted-theme.el b/modus-vivendi-tinted-theme.el
index 37971c7dfc..b3825e14d1 100644
--- a/modus-vivendi-tinted-theme.el
+++ b/modus-vivendi-tinted-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
diff --git a/modus-vivendi-tritanopia-theme.el
b/modus-vivendi-tritanopia-theme.el
index 13779913cb..2558655372 100644
--- a/modus-vivendi-tritanopia-theme.el
+++ b/modus-vivendi-tritanopia-theme.el
@@ -3,9 +3,8 @@
;; Copyright (C) 2019-2024 Free Software Foundation, Inc.
;; Author: Protesilaos Stavrou <info@protesilaos.com>
-;; Maintainer: Modus-Themes Development <~protesilaos/modus-themes@lists.sr.ht>
-;; URL: https://git.sr.ht/~protesilaos/modus-themes
-;; Mailing-List: https://lists.sr.ht/~protesilaos/modus-themes
+;; Maintainer: Protesilaos Stavrou <info@protesilaos.com>
+;; URL: https://github.com/protesilaos/modus-themes
;; Keywords: faces, theme, accessibility
;; This file is part of GNU Emacs.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] externals/modus-themes f4237bdb02 1/2: Update development links,
ELPA Syncer <=