emacs-elpa-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] externals/modus-themes 263e4f2572 5/5: Recompile the Info manual


From: ELPA Syncer
Subject: [elpa] externals/modus-themes 263e4f2572 5/5: Recompile the Info manual
Date: Sun, 3 Mar 2024 03:58:29 -0500 (EST)

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

    Recompile the Info manual
---
 doc/modus-themes.info | 408 +++++++++++++++++---------------------------------
 1 file changed, 136 insertions(+), 272 deletions(-)

diff --git a/doc/modus-themes.info b/doc/modus-themes.info
index 60d9f0808d..d33636d09d 100644
--- a/doc/modus-themes.info
+++ b/doc/modus-themes.info
@@ -1661,14 +1661,6 @@ line colorful.
 
    *note Add padding to mode line: DIY Add padding to the mode line.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Remove the border
      (setq modus-themes-common-palette-overrides
            '((border-mode-line-active unspecified)
@@ -1702,14 +1694,6 @@ borderless.
 
    *note Add padding to mode line: DIY Add padding to the mode line.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Blue background, neutral foreground, intense blue border
      (setq modus-themes-common-palette-overrides
            '((bg-mode-line-active bg-blue-intense)
@@ -1722,11 +1706,23 @@ borderless.
              (fg-mode-line-active fg-main)
              (border-mode-line-active blue-intense)))
 
-     ;; Subtle red background, red foreground, invisible border
+     ;; Sage (green/cyan) background, neutral foreground, slightly distinct 
green border
      (setq modus-themes-common-palette-overrides
-           '((bg-mode-line-active bg-red-subtle)
-             (fg-mode-line-active red-warmer)
-             (border-mode-line-active bg-red-subtle)))
+           '((bg-mode-line-active bg-sage)
+             (fg-mode-line-active fg-main)
+             (border-mode-line-active bg-green-intense)))
+
+     ;; As above, but with a purple style
+     (setq modus-themes-common-palette-overrides
+           '((bg-mode-line-active bg-lavender)
+             (fg-mode-line-active fg-main)
+             (border-mode-line-active bg-magenta-intense)))
+
+     ;; As above, but with an earthly style
+     (setq modus-themes-common-palette-overrides
+           '((bg-mode-line-active bg-ochre)
+             (fg-mode-line-active fg-main)
+             (border-mode-line-active bg-yellow-intense)))
 
    Reload the theme for changes to take effect.
 
@@ -1745,15 +1741,6 @@ affect the colors of the built-in ‘tab-bar-mode’ and 
‘tab-line-mode’.
 fringes, and line numbers.  These are shown in other sections of this
 manual.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Make the `tab-bar-mode' mode subtle while keepings its original
      ;; gray aesthetic.
      (setq modus-themes-common-palette-overrides
@@ -1796,14 +1783,6 @@ the fringe invisible or how to assign to it a 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.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Make the fringe invisible
      (setq modus-themes-common-palette-overrides
            '((fringe unspecified)))
@@ -1857,14 +1836,6 @@ prompts.
 
    *note Option for command prompt styles: Command prompts.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Keep the background unspecified (like the default), but use a faint
      ;; foreground color.
      (setq modus-themes-common-palette-overrides
@@ -1896,14 +1867,6 @@ matches.  We show three different degrees of intensity.
 
    *note Option for completion framework aesthetics: Completion UIs.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Add a nuanced background color to completion matches, while keeping
      ;; their foreground intact (foregrounds do not need to be specified in
      ;; this case, but we do it for didactic purposes).
@@ -1989,14 +1952,6 @@ syntax use the old alt-syntax style.
    *note Make use of alternative styles for code syntax: DIY Make use of
 alternative styles for code syntax.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Yellow comments and green strings like older versions of the Modus
      ;; themes
      (setq modus-themes-common-palette-overrides
@@ -2030,16 +1985,7 @@ 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:
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
-     ;; The old "alt-syntax"
+     ;; The old "alt-syntax" (before version 4.0.0 of the Modus themes)
      (setq modus-themes-common-palette-overrides
            '((builtin magenta)
              (comment fg-dim)
@@ -2125,15 +2071,6 @@ yellow and strings green.
    *note Make code syntax use the old alt-syntax style: DIY Make code
 syntax use the old alt-syntax style.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Mimic `ef-night' theme (from my `ef-themes') for code syntax
      ;; highlighting, while still using the Modus colors (and other
      ;; mappings).
@@ -2211,14 +2148,6 @@ underlines for those highlights.
 
    [ The ‘fg-paren-match’ is part of 4.4.0-dev.  ]
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Change the background to a shade of magenta
      (setq modus-themes-common-palette-overrides
            '((bg-paren-match bg-magenta-intense)))
@@ -2249,14 +2178,6 @@ buttons that appear in ‘M-x customize’ and related are 
distinct shades
 of gray.  The following set of overrides removes the gray from the
 active buttons and amplifies it for the inactive ones.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      (setq modus-themes-common-palette-overrides
            '((bg-button-active bg-main)
              (fg-button-active fg-main)
@@ -2283,14 +2204,6 @@ less colorful.
    *note Make inline code in prose use alternative styles: DIY Make
 inline code in prose use alternative styles.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Increase intensity
      (setq modus-themes-common-palette-overrides
            '((prose-done green-intense)
@@ -2324,15 +2237,6 @@ of the themes: the user can mix and match styles at will.
    *note Make TODO and DONE more intense: DIY Make TODO and DONE more or
 less intense.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Apply more colorful foreground to some headings (headings 0-8).
      ;; Level 0 is for Org #+title and related.
      (setq modus-themes-common-palette-overrides
@@ -2385,18 +2289,9 @@ contents and for the delimiter lines (the ‘#+begin_’ and 
‘#+end_’
 parts).  The text of the delimiter lines is a subtle gray foreground
 color.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Make code blocks (in Org, for example) use a more colorful style
      ;; for their delimiter lines as well as their contents.  Give this a
-     ;; purple feel.
+     ;; purple feel.  Make the delimiter lines distinct from the contents.
      (setq modus-themes-common-palette-overrides
            '((bg-prose-block-contents bg-magenta-nuanced)
              (bg-prose-block-delimiter bg-lavender)
@@ -2426,6 +2321,37 @@ color.
              (bg-prose-block-delimiter bg-ochre)
              (fg-prose-block-delimiter fg-main)))
 
+   The previous examples differentiate the delimiter lines from the
+block’s contents.  Though we can mimic the default aesthetic of a
+uniform background, while changing the applicable colors.  Here are some
+nice combinations:
+
+     ;; Solid green style.
+     (setq modus-themes-common-palette-overrides
+           '((bg-prose-block-contents bg-green-nuanced)
+             (bg-prose-block-delimiter bg-green-nuanced)
+             (fg-prose-block-delimiter green-warmer)))
+
+     ;; Solid yellow style.
+     (setq modus-themes-common-palette-overrides
+           '((bg-prose-block-contents bg-yellow-nuanced)
+             (bg-prose-block-delimiter bg-yellow-nuanced)
+             (fg-prose-block-delimiter yellow-cooler)))
+
+     ;; Solid cyan style.
+     (setq modus-themes-common-palette-overrides
+           '((bg-prose-block-contents bg-cyan-nuanced)
+             (bg-prose-block-delimiter bg-cyan-nuanced)
+             (fg-prose-block-delimiter cyan-cooler)))
+
+   [ Combine the above with a suitable mode line style for maximum
+effect (*note DIY Make the active mode line colorful::).  ]
+
+   Finally, the following makes code blocks have no distinct background.
+The minimal styles are applied to the delimiter lines, which only use a
+subtle gray foreground.  This was the default for the Modus themes up
+until version 4.3.0.
+
      ;; Make code blocks more minimal, so that (i) the delimiter lines have
      ;; no background, (ii) the delimiter foreground is a subtle gray, and
      ;; (iii) the block contents have no distinct background either.  This
@@ -2452,14 +2378,6 @@ third makes the agenda use various shades of blue.  Mix 
and match at
 will, while also combining these styles with what we show in the other
 chapters with practical stylistic variants.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
      ;; Make the Org agenda use alternative and varied colors.
      (setq modus-themes-common-palette-overrides
            '((date-common cyan)   ; default value (for timestamps and more)
@@ -2532,15 +2450,6 @@ permutation.
    *note Make TODO and DONE more or less intense: DIY Make TODO and DONE
 more or less intense.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; These are all the mappings at their default values for didactic
      ;; purposes
      (setq modus-themes-common-palette-overrides
@@ -2600,15 +2509,6 @@ Before we show the code, this is the anatomy of a 
message:
 
    We thus have the following:
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Reduce the intensity of mail citations and headers
      (setq modus-themes-common-palette-overrides
            '((mail-cite-0 cyan-faint)
@@ -2661,15 +2561,6 @@ foreground value.
    *note Do not extend the region background: DIY Do not extend the
 region background.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; A background with no specific foreground (use foreground of
      ;; underlying text)
      (setq modus-themes-common-palette-overrides
@@ -2700,15 +2591,6 @@ Stylistic variants using palette overrides.).  In the 
following code
 block we show how to affect the semantic color mapping that covers mouse
 hover effects and related highlights:
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Make the background an intense yellow
      (setq modus-themes-common-palette-overrides
            '((bg-hover bg-yellow-intense)))
@@ -2731,15 +2613,6 @@ Stylistic variants using palette overrides.).  Here we 
show how to
 affect the color of the underlines that are used by code linters and
 prose spell checkers.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Make the underlines less intense
      (setq modus-themes-common-palette-overrides
            '((underline-err red-faint)
@@ -2765,15 +2638,6 @@ the Modus themes (*note Stylistic variants using palette 
overrides: DIY
 Stylistic variants using palette overrides.).  In this section we show
 how to affect the ‘display-line-numbers-mode’.
 
-     ;; These overrides are common to all Modus themes.  We also provide
-     ;; theme-specific options, such as `modus-operandi-palette-overrides'.
-     ;;
-     ;; In general, the theme-specific overrides are better for overriding
-     ;; color values, such as redefining what `blue-faint' looks like.  The
-     ;; common overrides are best used for changes to semantic color
-     ;; mappings, as we show below.
-
-
      ;; Make line numbers less intense
      (setq modus-themes-common-palette-overrides
            '((fg-line-number-inactive "gray50")
@@ -6448,93 +6312,93 @@ Node: Advanced customization58548
 Node: DIY Palette override presets60207
 Node: DIY Stylistic variants using palette overrides63062
 Node: DIY Make the mode line borderless65116
-Node: DIY Make the active mode line colorful66905
-Node: DIY Make the tab bar more or less colorful69036
-Node: DIY Make the fringe invisible or another color71388
-Node: DIY Make links use subtle or no underlines73003
-Node: DIY Make prompts more or less colorful74121
-Node: DIY Make completion matches more or less colorful75858
-Node: DIY Make comments yellow and strings green79831
-Node: DIY Make code syntax use the old alt-syntax style81954
-Node: DIY Make use of alternative styles for code syntax85449
-Node: DIY Make matching parenthesis more or less intense89326
-Node: DIY Make box buttons more or less gray91168
-Node: DIY Make TODO and DONE more or less intense92595
-Node: DIY Make headings more or less colorful94510
-Node: DIY Make Org block colors more or less colorful97042
-Node: DIY Make Org agenda more or less colorful100334
-Node: DIY Make inline code in prose use alternative styles103923
-Node: DIY Make mail citations and headers more or less colorful106628
-Node: DIY Make the region preserve text colors plus other styles109443
-Node: DIY Make mouse highlights more or less colorful111414
-Node: DIY Make language underlines less colorful112842
-Node: DIY Make line numbers use alternative styles114409
-Node: DIY Make diffs use only a foreground116467
-Node: DIY Make deuteranopia diffs red and blue instead of yellow and 
blue119358
-Node: DIY More accurate colors in terminal emulators121838
-Node: DIY Range of color with terminal emulators123150
-Node: DIY Per-theme customization settings125943
-Node: DIY Do not extend the region background127376
-Node: DIY Add padding to the mode line128180
-Node: DIY Remap face with local value131113
-Node: DIY Font configurations for Org and others133661
-Ref: DIY Font configurations for Org and others-Footnote-1136644
-Node: DIY Configure bold and italic faces136831
-Node: DIY Custom Org todo keyword and priority faces141453
-Node: DIY Custom Org emphasis faces145196
-Node: DIY Use colored Org source blocks per language150077
-Node: DIY Measure color contrast154717
-Node: DIY Load theme depending on time of day157437
-Node: DIY Backdrop for pdf-tools158467
-Node: DIY Toggle themes without reloading them161636
-Node: DIY Use more spacious margins or padding in Emacs frames162945
-Node: DIY Custom hl-todo colors167202
-Node: DIY Add support for solaire-mode169019
-Node: DIY Use a hook at the post-load-theme phase172145
-Node: DIY A theme-agnostic hook for theme loading174269
-Node: Face coverage176900
-Node: Supported packages177352
-Node: Indirectly covered packages183062
-Node: Notes on individual packages184431
-Node: Note on calendarel weekday and weekend colors185531
-Node: Note on git-gutter in Doom Emacs186679
-Node: Note on php-mode multiline comments189179
-Node: Note on underlines in compilation buffers189939
-Node: Note on inline Latex in Org buffers190811
-Node: Note on dimmerel191421
-Node: Note on display-fill-column-indicator-mode192906
-Node: Note on highlight-parenthesesel194359
-Node: Note on mmm-modeel background colors200442
-Node: Note for prism202796
-Node: Note on company-mode overlay pop-up206018
-Ref: Note on company-mode overlay pop-up-Footnote-1206748
-Ref: Note on company-mode overlay pop-up-Footnote-2206815
-Node: Note on ERC escaped color sequences206870
-Ref: Note on ERC escaped color sequences-Footnote-1208298
-Node: Note on powerline or spaceline208408
-Node: Note on SHR colors208822
-Node: Note on SHR fonts209246
-Node: Note on Ement colors and fonts209933
-Node: Note on pdf-tools link hints211443
-Node: Note on the Notmuch logo213903
-Node: Note on goto-address-mode faces214441
-Node: Frequently Asked Questions215559
-Node: Is the contrast ratio about adjacent colors?216192
-Node: What does it mean to avoid exaggerations?217701
-Node: Why are colors mostly variants of blue magenta cyan?219553
-Node: What is the best setup for legibility?223887
-Node: Are these color schemes?226534
-Node: Port the Modus themes to other platforms?230218
-Node: Contributing233064
-Node: Sources of the themes233463
-Node: Issues you can help with234359
-Node: Patches require copyright assignment to the FSF235752
-Node: Acknowledgements237974
-Node: GNU Free Documentation License242144
-Node: Indices267508
-Node: Function index267687
-Node: Variable index268985
-Node: Concept index271679
+Node: DIY Make the active mode line colorful66491
+Node: DIY Make the tab bar more or less colorful68709
+Node: DIY Make the fringe invisible or another color70646
+Node: DIY Make links use subtle or no underlines71847
+Node: DIY Make prompts more or less colorful72965
+Node: DIY Make completion matches more or less colorful74288
+Node: DIY Make comments yellow and strings green77847
+Node: DIY Make code syntax use the old alt-syntax style79556
+Node: DIY Make use of alternative styles for code syntax82679
+Node: DIY Make matching parenthesis more or less intense86141
+Node: DIY Make box buttons more or less gray87569
+Node: DIY Make TODO and DONE more or less intense88582
+Node: DIY Make headings more or less colorful90083
+Node: DIY Make Org block colors more or less colorful92200
+Node: DIY Make Org agenda more or less colorful96460
+Node: DIY Make inline code in prose use alternative styles99635
+Node: DIY Make mail citations and headers more or less colorful101925
+Node: DIY Make the region preserve text colors plus other styles104325
+Node: DIY Make mouse highlights more or less colorful105881
+Node: DIY Make language underlines less colorful106894
+Node: DIY Make line numbers use alternative styles108046
+Node: DIY Make diffs use only a foreground109689
+Node: DIY Make deuteranopia diffs red and blue instead of yellow and 
blue112580
+Node: DIY More accurate colors in terminal emulators115060
+Node: DIY Range of color with terminal emulators116372
+Node: DIY Per-theme customization settings119165
+Node: DIY Do not extend the region background120598
+Node: DIY Add padding to the mode line121402
+Node: DIY Remap face with local value124335
+Node: DIY Font configurations for Org and others126883
+Ref: DIY Font configurations for Org and others-Footnote-1129866
+Node: DIY Configure bold and italic faces130053
+Node: DIY Custom Org todo keyword and priority faces134675
+Node: DIY Custom Org emphasis faces138418
+Node: DIY Use colored Org source blocks per language143299
+Node: DIY Measure color contrast147939
+Node: DIY Load theme depending on time of day150659
+Node: DIY Backdrop for pdf-tools151689
+Node: DIY Toggle themes without reloading them154858
+Node: DIY Use more spacious margins or padding in Emacs frames156167
+Node: DIY Custom hl-todo colors160424
+Node: DIY Add support for solaire-mode162241
+Node: DIY Use a hook at the post-load-theme phase165367
+Node: DIY A theme-agnostic hook for theme loading167491
+Node: Face coverage170122
+Node: Supported packages170574
+Node: Indirectly covered packages176284
+Node: Notes on individual packages177653
+Node: Note on calendarel weekday and weekend colors178753
+Node: Note on git-gutter in Doom Emacs179901
+Node: Note on php-mode multiline comments182401
+Node: Note on underlines in compilation buffers183161
+Node: Note on inline Latex in Org buffers184033
+Node: Note on dimmerel184643
+Node: Note on display-fill-column-indicator-mode186128
+Node: Note on highlight-parenthesesel187581
+Node: Note on mmm-modeel background colors193664
+Node: Note for prism196018
+Node: Note on company-mode overlay pop-up199240
+Ref: Note on company-mode overlay pop-up-Footnote-1199970
+Ref: Note on company-mode overlay pop-up-Footnote-2200037
+Node: Note on ERC escaped color sequences200092
+Ref: Note on ERC escaped color sequences-Footnote-1201520
+Node: Note on powerline or spaceline201630
+Node: Note on SHR colors202044
+Node: Note on SHR fonts202468
+Node: Note on Ement colors and fonts203155
+Node: Note on pdf-tools link hints204665
+Node: Note on the Notmuch logo207125
+Node: Note on goto-address-mode faces207663
+Node: Frequently Asked Questions208781
+Node: Is the contrast ratio about adjacent colors?209414
+Node: What does it mean to avoid exaggerations?210923
+Node: Why are colors mostly variants of blue magenta cyan?212775
+Node: What is the best setup for legibility?217109
+Node: Are these color schemes?219756
+Node: Port the Modus themes to other platforms?223440
+Node: Contributing226286
+Node: Sources of the themes226685
+Node: Issues you can help with227581
+Node: Patches require copyright assignment to the FSF228974
+Node: Acknowledgements231196
+Node: GNU Free Documentation License235366
+Node: Indices260730
+Node: Function index260909
+Node: Variable index262207
+Node: Concept index264901
 
 End Tag Table
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]