Update to modus-themes version 4.1.0

This commit is contained in:
Protesilaos Stavrou 2023-02-22 19:56:22 +02:00
parent d9d8463713
commit 829d06d9d3
No known key found for this signature in database
GPG key ID: 99BD6459CD5CA3EA
4 changed files with 437 additions and 140 deletions

View file

@ -15,6 +15,319 @@ For further details, please consult these additional resources:
+ Manual :: <https://protesilaos.com/emacs/modus-themes>
+ Screenshots :: <https://protesilaos.com/emacs/modus-themes-pictures>
* 4.1.0
:PROPERTIES:
:CUSTOM_ID: h:d028f117-8a74-4c0c-b838-9f6bf2b43c19
:END:
** Recursive semantic colour mapping
:PROPERTIES:
:CUSTOM_ID: h:262e2f5f-4db0-4549-a5ba-4e57cd2edc6a
:END:
Version 4 of the Modus themes changed how all colour-related
customisations are done. Instead of multiple user options with
hard-coded stylistic presets, users have access to a comprehensive
system of "named colours" and "semantic colour mappings". The former
is an association between a name, like =blue-warmer=, and a colour
value such as =#3548cf=. While semantic colour mappings are
associations between syntactic/interface constructs and named colours,
such as what value level 2 headings have.
When overriding the palette users can now define semantic colour
mappings whose value is another such mapping. This recursion
simplifies how multiple overrides are defined.
The manual offers extensive guidance on the topic of palette
overrides. There are many sections that include code samples that are
ready for use.
The addition of recursive semantic colour mappings solves a problem
reported by Imran Khan on the mailing list where they were trying to
do what made sense (recursion) but the old code did not permit as
much:
<https://lists.sr.ht/~protesilaos/modus-themes/%3Cb7ca4702162fd575593f8ded28d9a888.contact%40imrankhan.live%3E>.
I was aware of that constraint from before the release of version
4.0.0 but was hesitant to implement recursion prior to getting some
feedback on the new palette overriding feature.
Also thanks to Christian Tietze for participating in that discussion
on the mailing list.
** Extract an arbitrary colour from a given theme's palette
:PROPERTIES:
:CUSTOM_ID: h:6ba1437f-e55f-4c3a-9c03-b0035293b4a2
:END:
I formalised the function ~modus-themes-get-color-value~ and
documented it at length. It accepts a =COLOR= argument, which
represents an entry in the palette (named colour or semantic colour
value), as well as optional =OVERRIDES= and =THEME= arguments. When
=OVERRIDES= is non-nil, ~modus-themes-get-color-value~ will read from
the overrides, otherwise it will only consult the default palette
value. The =THEME= argument specifies which theme's palette to use.
In the absence of =THEME=, the current one is used.
I already had the "get colour" functionality internally, but was
inspired to make it public after checking Sacha Chua's blog post
"Making highlight-sexp follow modus-themes-toggle":
<https://sachachua.com/blog/2023/01/making-highlight-sexp-follow-modus-themes-toggle/>.
Sacha was using a private function from the themes, which would have
been problematic if I would ever move things around.
Remember to read the documentation of ~modus-themes-list-colors~.
That command shows a preview of the named colours. When called with a
prefix argument (=C-u= by default), it shows a preview of the semantic
colour mappings.
** Option to disable other themes while loading Modus
:PROPERTIES:
:CUSTOM_ID: h:5af072da-38f6-44d0-9342-e799f0196006
:END:
In the past, we used to disable all other themes while loading a Modus
theme. I revised this for version 4 because I learnt that some users
use "themes" as bundles of arbitrary configurations.
With the addition of the ~modus-themes-disable-other-themes~ user
option, which is non-nil by default, I am restoring the old behaviour:
when loading a Modus theme all other themes are disabled.
This happens when the theme is loaded with the commands
~modus-themes-toggle~ and ~modus-themes-select~, or via Lisp with the
function ~modus-themes-load-theme~.
Users who need to run multiple themes can set this option to a nil
value. (Personally, I use minor modes for such stylistic bundles and
never have to worry about ~(mapc #'disable-theme custom-enabled-themes)~.)
Thanks to Tony Zorman for the feedback on the mailing list, which led
me to the introduction of this user option:
<https://lists.sr.ht/~protesilaos/modus-themes/%3C874jtew0gp.fsf%40hyperspace%3E#%3C87bkne84d2.fsf@hyperspace%3E>.
** Renamed the named colours for bg-{added,changed,removed}-intense
:PROPERTIES:
:CUSTOM_ID: h:d43ef5cb-10dd-4c33-9429-2289a5fb2506
:END:
They are now called ~bg-added-fringe~, ~bg-changed-fringe~,
~bg-removed-fringe~. Please update any palette overrides to reflect
this renaming.
** Documented how to override diffs for more optional combinations
:PROPERTIES:
:CUSTOM_ID: h:220d4361-7245-4632-998e-c0e2ee3b5f7d
:END:
The manual includes details (with copy-pastable code) on how to
achieve foreground-only diffs and/or how to have red+blue diffs
instead of the default red+green or the deuteranopia yellow+blue.
Thanks to Andrew Tropin for requesting this feature. We used to
provide this style in earlier versions of the themes, but now it is
much more flexible. Andrew's request was done via a private channel
and the information is shared with permission.
[ Since we are here, also thanks to Andrew for keeping the Guix
package of the Modus themes up to date. ]
** Stylistic changes
:PROPERTIES:
:CUSTOM_ID: h:fdcff629-22c1-4203-9104-4f732c59f731
:END:
- Guaranteed consistency between all of the line-related faces of the
~consult~ package. We use the ~shadow~ face in all interfaces where
line numbers are contextual information (Occur, Grep,...). With
Consult, this was not the case for commands like ~consult-line~.
Thanks to Daniel Mendler (also known as @minad) for bringing this
matter to my attention:
<https://lists.sr.ht/~protesilaos/ef-themes/%3Cb03413a6-cb77-615d-145d-db4eb710bfca%40daniel-mendler.de%3E>.
- Refined all diff colours for fringes and reduced the saturation for
added lines in ~modus-operandi-deuteranopia~, ~modus-vivendi-deuteranopia-theme~.
Thanks to Andrew Tropin for showing me some usability issues with
the previous styles. This was done via a private channel and the
information is shared with permission.
- Instructed the ~dashboard~ icons to retain their underlying colour.
The default value of the ~dashboard-items-face~ made all icons use
the same colour, detracting from their distinctiveness. Thanks to
Thanos Apollo for bringing this matter to my attention. It was done
via a private channel and the information is shared with permission.
- Amplified the intensity of the =#+begin_src= text when the user
option opts for ~(setq modus-themes-org-blocks 'gray-background)~.
The text is now easier to discern. That user option makes the
inside of the block have a gray background and the begin/end lines
to have a more intense gray, giving off a "blocky" impression.
- Made the ~compilation-warning~ face also inherit the
~modus-themes-bold~ face. This means that it responds to the value
of the user option ~modus-themes-bold-constructs~, the same way the
other compilation-related mode line faces do. Thanks to Manuel
Giraud for informing me about the inconsistency in
~compilation-warning~. This was done via a private channel and the
information is shared with permission.
- Calibrated the hueness of the "nuanced" backgrounds in the
~modus-operandi-tinted~ and ~modus-vivendi-tinted~ themes. These
tweaks are necessary to retain thematic consistency.
- Reset ~mu4e-header-highlight-face~ to its intended style. I made a
mistake before: I did not want the ~highlight~ face to be used in
this case as it is too intense. Sorry!
- Toned down the highlight line of the ~ctrlf~ and ~swiper~ packages.
I mistakenly used the ~highlight~ before, which is too intense for
the purposes of an ancillary background colour.
- Applied "nuanced" backgrounds to the tinted Org blocks. This fixes
an error of mine where I amplified the background colouration of Org
blocks. This concerns the case where the user option
~modus-themes-org-blocks~ has a =tinted-background= value. Thanks
to Mark Bestley for informing me about this in issue 60 on the
GitHub mirror:
<https://github.com/protesilaos/modus-themes/issues/60#issuecomment-1374530488>.
- Removed the hardcoding of the ~italic~ style in three faces, opting
instead to make them subject to the user option ~modus-themes-italic-constructs~.
The faces are ~marginalia-documentation~, ~markup-attribute-face~,
and ~org-agenda-calendar-sexp~.
- Tweaked the Org agenda deadline and today schedule to use a bold
weight only when the user option ~modus-themes-bold-constructs~ is
set to a non-nil value. Thanks to Marko Kocic for reporting an
issue that brought this matter to my attention:
- <https://lists.sr.ht/~protesilaos/modus-themes/%3C35588839.256749.1673272214728%40office.mailbox.org%3E>
- <https://lists.sr.ht/~protesilaos/modus-themes/%3C874jszvk5g.fsf%40protesilaos.com%3E>
- <https://lists.sr.ht/~protesilaos/modus-themes/%3C87ilhfu101.fsf%40protesilaos.com%3E>
- Enforced the main foreground colour in the faces =highlight= and
=secondary-selection=. This should have always been there to avoid
awkward colour combinations. I realised it was missing after
corresponding with Edgar Vincent on a relevant topic:
<https://lists.sr.ht/~protesilaos/modus-themes/%3C878ri95h1q.fsf%40posteo.net%3E#%3C87ilhc7usc.fsf@posteo.net%3E>.
- Made the ~eglot-mode-line~ face conditionally bold, by subjecting it
to the user option ~modus-themes-bold-constructs~.
- Ensure that the background of the ~company~ package's popup is the
same as that of the ~corfu~ package. This is a subtle neutral
value.
- Fixed the hue of the ~org-habit~ "ready" faces. It should be green
and I made a mistake here. The ~modus-operandi-deuteranopia~ and
~modus-vivendi-deuteranopia~ themes do change the underlying hues
though, as green is not suitable for them.
- Simplified the ~keycast~ faces so that (i) they do not use a =:box=
attribute that can look awkward in some cases and (ii) the name of
the given command is not colourised to avoid exaggerations with the
use of colour.
- Made the ~powerline-active1~ face inherit from ~mode-line~ instead
of ~mode-line-active~. The latter only exists in newer versions of
Emacs and we do not want to make the themes break in older versions.
Thanks to TitusMu for identifying this and reporting it in issue 64 on
the GitHub mirror: <https://github.com/protesilaos/modus-themes/issues/64>.
- Decoupled all ~ediff~ faces from their ~diff-mode~ counterparts.
Ediff does not depend on ~diff-mode~, so we want to make each set of
faces stand on its own. Thanks to Bernd Rellermeyer for pointing
out this implicit dependency in issue 68 on the GitHub mirror:
<https://github.com/protesilaos/modus-themes/issues/68>.
** Miscellaneous
:PROPERTIES:
:CUSTOM_ID: h:14d1f1b0-00e0-4275-a06c-9e34daf6411a
:END:
- Improved the clarity and robustness of the code that does the work
of ~modus-themes-list-colors~.
- Refined the colour value of the =blue-warmer= named colour for all
the light themes. It is a tiny bit darker than before.
- Introduced a ~t~ fallback value for the user option
~modus-themes-completions~. It makes it easier to apply the same
styles for the selection line and matching characters.
- Documented how to not extend the active region background.
- Explained how to make tabs more or less colourful by using palette
overrides.
- Removed obsolete and redundant statements from the documentation the
user option ~modus-themes-completions~. There was (i) an outdated
reference to the =background= value, which is no longer supported,
and (ii) a statement about the standard Completions' buffer that was
not useful. Thanks to Rudolf Adamkovič for informing me about this:
<https://lists.sr.ht/~protesilaos/modus-themes/%3Cm2tu1211qz.fsf%40me.com%3E>.
- Rephrase the statement ="*Completions* buffer"= in the documentation
in the interest of clarity. Thanks to Rudolf Adamkovič for the
suggestion:
<https://lists.sr.ht/~protesilaos/modus-themes/%3Cm2tu1211qz.fsf%40me.com%3E#%3Cm2eds43htz.fsf@me.com%3E>.
- Updated the sample configuration of the themes with ~use-package~ in
the interest of simplicity. Thanks to Sergey Nichiporchik for the
contribution. Sergey's contribution is within the ~15 line limit
and thus does not require copyright assignment to the Free Software
Foundation.
This was done in merge request 59 on the GitLab mirror:
<https://gitlab.com/protesilaos/modus-themes/-/merge_requests/59>.
The prepatory discussion took place in issue 310 on the same mirror:
<https://gitlab.com/protesilaos/modus-themes/-/issues/310>.
Weeks later I further simplified the relevant samples for the sake
of uniformity with the generic package setup. Thanks to Zoltan
Kiraly for informing me about the fact that the ~:bind~ keyword
delays the load of the package until the given command is invoked:
<https://github.com/protesilaos/modus-themes/pull/67>.
Streamlining the configuration makes it easier for me to propose one
set of basic configurations without the need to know what a
configuration macro is doing behind the scenes.
- Fixed an example colour in the documentation. Thanks to Russell Sim
for spotting the error of me using =bg-blue= instead of
=bg-blue-intense=:
<https://lists.sr.ht/~protesilaos/modus-themes/%3Cyger0wa9gsn.fsf%40simopolis.xyz%3E>.
- Defined the missing =modus-themes-nuanced-{red,green,yellow,blue,magenta,cyan}= faces.
Those are used internally to avoid repetition, though users can also
rely on them for their personal configurations (same for all other
Modus faces).
- Improved the documentation on how to have a borderless mode line
style by using the palette overrides.
- Updated the manual's entry on the ~pdf-tools~ backdrop to make it
use the new conventions that have been in place since version 4 of
the themes. Thanks to Utkarsh Singh for the patches:
<https://lists.sr.ht/~protesilaos/modus-themes/patches/37902>.
- Add an explicit notice that the version of the themes that is built
into Emacs must use the ~require-theme~ function instead of the
familiar ~require~. Built-in themes are not considered "code", due
to old conventions, and are not part of the ~load-path~ that
~require~ reads from. This is not up to the theme to decide.
Interested users must simply know about this important technicality.
Thanks to Koen van Greevenbroek for reporting the problem that
helped me identify this issue:
<https://lists.sr.ht/~protesilaos/modus-themes/%3C31038fd76868fa3d07c9a429dfed8fd6ac374bb8.camel%40posteo.net%3E>.
- Clarified the wording of the ~modus-themes-with-colors~ setup for
custom faces. It explains when this macro should be called. Thanks
to user bangedorrunt for the feedback in issue 59 on the GitHub
mirror: <https://github.com/protesilaos/modus-themes/issues/59>.
* 4.0.0
:PROPERTIES:
:CUSTOM_ID: h:cd353ccc-daf5-4ee5-885a-b3f21be92b66

View file

@ -43,11 +43,11 @@ customization options for the Modus themes, and provides every other
piece of information pertinent to them.
The documentation furnished herein corresponds to stable version
4.0.0, released on 2023-01-01. Any reference to a newer feature which
4.1.0, released on 2023-02-22. Any reference to a newer feature which
does not yet form part of the latest tagged commit, is explicitly marked
as such.
Current development target is 4.1.0-dev.
Current development target is 4.2.0-dev.
• Package name (GNU ELPA): modus-themes
• Official manual: <https://protesilaos.com/emacs/modus-themes>
@ -770,9 +770,7 @@ File: modus-themes.info, Node: Disable other themes, Next: Bold constructs, P
4.2 Option for disabling other themes while loading Modus
=========================================================
[ Part of 4.1.0-dev. ]
Brief: Disable all other themes when loading a Modus theme.
Brief: Disable all other themes when loading a Modus theme.
Symbol: modus-themes-disable-other-themes (boolean type)
@ -2394,17 +2392,15 @@ File: modus-themes.info, Node: Make diffs use only a foreground, Next: Make de
4.11.2.22 Make diffs use only a foreground
..........................................
[ Part of 4.1.0-dev. ]
This is one of our practical examples to override the semantic colors
of the Modus themes (*note Stylistic variants using palette
overrides::). In this section we show how to change diff buffers (e.g.
in magit) to 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” overrides.
This is one of our practical examples to override the semantic colors of
the Modus themes (*note Stylistic variants using palette overrides::).
In this section we show how to change diff buffers (e.g. in magit) to
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”
overrides.
;; Diffs with only foreground colours. Word-wise ("refined") diffs
;; have a gray background to draw attention to themselves.
@ -2459,12 +2455,10 @@ File: modus-themes.info, Node: Make deuteranopia diffs red and blue instead of
4.11.2.23 Make deuteranopia diffs red and blue instead of yellow and blue
.........................................................................
[ Part of 4.1.0-dev. ]
This is one of our practical examples to override the semantic colors
of the Modus themes (*note Stylistic variants using palette
overrides::). In this section we show how to implement a red+blue color
coding for diffs in the themes modus-operandi-deuteranopia and
This is one of our practical examples to override the semantic colors of
the Modus themes (*note Stylistic variants using palette overrides::).
In this section we show how to implement a red+blue color coding for
diffs in the themes modus-operandi-deuteranopia and
modus-vivendi-deuteranopia. As those themes are optimized for users
with red-green color deficiency, they do not use the typical red+green
color coding for diffs, defaulting instead to yellow+blue which are
@ -2722,9 +2716,7 @@ File: modus-themes.info, Node: Get a single color from the palette, Next: Use
5.5 Get a single color from the palette
=======================================
[ Part of 4.1.0-dev. ]
*note Use theme colors in code with modus-themes-with-colors::.
*note Use theme colors in code with modus-themes-with-colors::.
The fuction modus-themes-get-color-value can be called from Lisp to
return the value of a color from the active Modus theme palette. It
@ -3745,7 +3737,7 @@ have lots of extensions, so the “full support” may not be 100% true…
• csv-mode
• ctrlf
• custom (what you get with M-x customize)
• dashboard [part of 4.1.0-dev]
• dashboard
• deadgrep
• deft
• devdocs
@ -5788,7 +5780,7 @@ B.1 Function index
* modus-themes-contrast: Measure color contrast.
(line 6)
* modus-themes-get-color-value: Get a single color from the palette.
(line 10)
(line 8)
* modus-themes-list-colors: Preview theme colors. (line 6)
* modus-themes-list-colors-current: Preview theme colors. (line 12)
* modus-themes-load-theme: Enable and load. (line 6)
@ -5922,106 +5914,106 @@ Node: Differences between loading and enabling22702
Node: Customization options24740
Node: Custom reload theme28488
Node: Disable other themes29396
Node: Bold constructs30604
Node: Italic constructs31441
Node: Mixed fonts32212
Node: Command prompts33208
Node: Completion UIs35013
Node: Org mode blocks37803
Node: Heading styles39683
Node: UI typeface44037
Node: Palette overrides44968
Node: Palette override presets49275
Node: Stylistic variants using palette overrides51772
Node: Make the mode line borderless53579
Node: Make the active mode line colorful55187
Node: Make the tab bar more or less colorful57138
Node: Make the fringe invisible or another color59375
Node: Make links use subtle or no underlines60875
Node: Make prompts more or less colorful61878
Node: Make completion matches more or less colorful63548
Node: Make comments yellow and strings green67454
Node: Make code syntax use the old alt-syntax style69363
Node: Make use of alternative styles for code syntax72650
Node: Make matching parenthesis more or less intense76320
Node: Make box buttons more or less gray77762
Node: Make TODO and DONE more or less intense79074
Node: Make headings more or less colorful80783
Node: Make Org agenda more or less colorful83189
Node: Make inline code in prose use alternative styles85927
Node: Make mail citations and headers more or less colorful88474
Node: Make the region preserve text colors plus other styles91175
Node: Make mouse highlights more or less colorful92992
Node: Make language underlines less colorful94305
Node: Make line numbers use alternative styles95757
Node: Make diffs use only a foreground97700
Node: Make deuteranopia diffs red and blue instead of yellow and blue100504
Node: Advanced customization102902
Node: More accurate colors in terminal emulators104432
Node: Range of color with terminal emulators105673
Node: Preview theme colors108387
Node: Per-theme customization settings110232
Node: Get a single color from the palette111578
Node: Use theme colors in code with modus-themes-with-colors113810
Node: Do not extend the region background116143
Node: Add padding to mode line116941
Node: Remap face with local value119497
Node: Font configurations for Org and others121918
Ref: Font configurations for Org and others-Footnote-1124827
Node: Configure bold and italic faces125014
Node: Custom Org todo keyword and priority faces129171
Node: Custom Org emphasis faces132736
Node: Update Org block delimiter fontification137559
Node: Measure color contrast139476
Node: Load theme depending on time of day142174
Node: Backdrop for pdf-tools143184
Node: Toggle themes without reloading them146083
Node: A theme-agnostic hook for theme loading147359
Node: Custom hl-todo colors149781
Node: Add support for solaire-mode151306
Node: Face coverage154217
Node: Supported packages154669
Node: Indirectly covered packages160038
Node: Notes on individual packages161391
Node: Note on calendarel weekday and weekend colors162491
Node: Note on git-gutter in Doom Emacs163639
Node: Note on php-mode multiline comments165983
Node: Note on underlines in compilation buffers166736
Node: Note on inline Latex in Org buffers167573
Node: Note on dimmerel168183
Node: Note on display-fill-column-indicator-mode169668
Node: Note on highlight-parenthesesel171067
Node: Note on mmm-modeel background colors177045
Node: Note for prism179345
Node: Note on company-mode overlay pop-up182513
Ref: Note on company-mode overlay pop-up-Footnote-1183243
Ref: Note on company-mode overlay pop-up-Footnote-2183310
Node: Note on ERC escaped color sequences183365
Ref: Note on ERC escaped color sequences-Footnote-1184793
Node: Note on powerline or spaceline184903
Node: Note on SHR colors185317
Node: Note on SHR fonts185741
Node: Note on Ement colors and fonts186380
Node: Note on pdf-tools link hints187890
Node: Note on the Notmuch logo190350
Node: Note on goto-address-mode faces190888
Node: Frequently Asked Questions192000
Node: Is the contrast ratio about adjacent colors?192631
Node: What does it mean to avoid exaggerations?194138
Node: Why are colors mostly variants of blue magenta cyan?195988
Node: What is the best setup for legibility?200294
Node: Are these color schemes?202939
Node: Port the Modus themes to other platforms?206621
Node: Contributing209393
Node: Sources of the themes209790
Node: Issues you can help with210684
Node: Patches require copyright assignment to the FSF212075
Node: Acknowledgements214295
Node: GNU Free Documentation License218226
Node: Indices243590
Node: Function index243769
Node: Variable index244952
Node: Concept index246851
Node: Bold constructs30576
Node: Italic constructs31413
Node: Mixed fonts32184
Node: Command prompts33180
Node: Completion UIs34985
Node: Org mode blocks37775
Node: Heading styles39655
Node: UI typeface44009
Node: Palette overrides44940
Node: Palette override presets49247
Node: Stylistic variants using palette overrides51744
Node: Make the mode line borderless53551
Node: Make the active mode line colorful55159
Node: Make the tab bar more or less colorful57110
Node: Make the fringe invisible or another color59347
Node: Make links use subtle or no underlines60847
Node: Make prompts more or less colorful61850
Node: Make completion matches more or less colorful63520
Node: Make comments yellow and strings green67426
Node: Make code syntax use the old alt-syntax style69335
Node: Make use of alternative styles for code syntax72622
Node: Make matching parenthesis more or less intense76292
Node: Make box buttons more or less gray77734
Node: Make TODO and DONE more or less intense79046
Node: Make headings more or less colorful80755
Node: Make Org agenda more or less colorful83161
Node: Make inline code in prose use alternative styles85899
Node: Make mail citations and headers more or less colorful88446
Node: Make the region preserve text colors plus other styles91147
Node: Make mouse highlights more or less colorful92964
Node: Make language underlines less colorful94277
Node: Make line numbers use alternative styles95729
Node: Make diffs use only a foreground97672
Node: Make deuteranopia diffs red and blue instead of yellow and blue100449
Node: Advanced customization102818
Node: More accurate colors in terminal emulators104348
Node: Range of color with terminal emulators105589
Node: Preview theme colors108303
Node: Per-theme customization settings110148
Node: Get a single color from the palette111494
Node: Use theme colors in code with modus-themes-with-colors113698
Node: Do not extend the region background116031
Node: Add padding to mode line116829
Node: Remap face with local value119385
Node: Font configurations for Org and others121806
Ref: Font configurations for Org and others-Footnote-1124715
Node: Configure bold and italic faces124902
Node: Custom Org todo keyword and priority faces129059
Node: Custom Org emphasis faces132624
Node: Update Org block delimiter fontification137447
Node: Measure color contrast139364
Node: Load theme depending on time of day142062
Node: Backdrop for pdf-tools143072
Node: Toggle themes without reloading them145971
Node: A theme-agnostic hook for theme loading147247
Node: Custom hl-todo colors149669
Node: Add support for solaire-mode151194
Node: Face coverage154105
Node: Supported packages154557
Node: Indirectly covered packages159906
Node: Notes on individual packages161259
Node: Note on calendarel weekday and weekend colors162359
Node: Note on git-gutter in Doom Emacs163507
Node: Note on php-mode multiline comments165851
Node: Note on underlines in compilation buffers166604
Node: Note on inline Latex in Org buffers167441
Node: Note on dimmerel168051
Node: Note on display-fill-column-indicator-mode169536
Node: Note on highlight-parenthesesel170935
Node: Note on mmm-modeel background colors176913
Node: Note for prism179213
Node: Note on company-mode overlay pop-up182381
Ref: Note on company-mode overlay pop-up-Footnote-1183111
Ref: Note on company-mode overlay pop-up-Footnote-2183178
Node: Note on ERC escaped color sequences183233
Ref: Note on ERC escaped color sequences-Footnote-1184661
Node: Note on powerline or spaceline184771
Node: Note on SHR colors185185
Node: Note on SHR fonts185609
Node: Note on Ement colors and fonts186248
Node: Note on pdf-tools link hints187758
Node: Note on the Notmuch logo190218
Node: Note on goto-address-mode faces190756
Node: Frequently Asked Questions191868
Node: Is the contrast ratio about adjacent colors?192499
Node: What does it mean to avoid exaggerations?194006
Node: Why are colors mostly variants of blue magenta cyan?195856
Node: What is the best setup for legibility?200162
Node: Are these color schemes?202807
Node: Port the Modus themes to other platforms?206489
Node: Contributing209261
Node: Sources of the themes209658
Node: Issues you can help with210552
Node: Patches require copyright assignment to the FSF211943
Node: Acknowledgements214163
Node: GNU Free Documentation License218094
Node: Indices243458
Node: Function index243637
Node: Variable index244820
Node: Concept index246719

End Tag Table

View file

@ -4,9 +4,9 @@
#+language: en
#+options: ':t toc:nil author:t email:t num:t
#+startup: content
#+macro: stable-version 4.0.0
#+macro: release-date 2023-01-01
#+macro: development-version 4.1.0-dev
#+macro: stable-version 4.1.0
#+macro: release-date 2023-02-22
#+macro: development-version 4.2.0-dev
#+macro: file @@texinfo:@file{@@$1@@texinfo:}@@
#+macro: space @@texinfo:@: @@
#+macro: kbd @@texinfo:@kbd{@@$1@@texinfo:}@@
@ -586,8 +586,6 @@ the user must manually reload the theme ([[#h:3f3c3728-1b34-437d-9d0c-b110f5b161
:end:
#+vindex: modus-themes-disable-other-themes
[ Part of {{{development-version}}}. ]
Brief: Disable all other themes when loading a Modus theme.
Symbol: ~modus-themes-disable-other-themes~ (=boolean= type)
@ -2259,8 +2257,6 @@ this section we show how to affect the ~display-line-numbers-mode~.
:CUSTOM_ID: h:b3761482-bcbf-4990-a41e-4866fb9dad15
:END:
[ Part of {{{development-version}}}. ]
This is one of our practical examples to override the semantic colors
of the Modus themes ([[#h:df1199d8-eaba-47db-805d-6b568a577bf3][Stylistic variants using palette overrides]]). In
this section we show how to change diff buffers (e.g. in ~magit~) to
@ -2325,8 +2321,6 @@ just using the "common" overrides.
:CUSTOM_ID: h:16389ea1-4cb6-4b18-9409-384324113541
:END:
[ Part of {{{development-version}}}. ]
This is one of our practical examples to override the semantic colors
of the Modus themes ([[#h:df1199d8-eaba-47db-805d-6b568a577bf3][Stylistic variants using palette overrides]]). In
this section we show how to implement a red+blue color coding for
@ -2569,8 +2563,6 @@ For a more elaborate design, it is better to inspect the source code of
:CUSTOM_ID: h:1cc552c1-5f5f-4a56-ae78-7b69e8512c4e
:END:
[ Part of {{{development-version}}}. ]
[[#h:51ba3547-b8c8-40d6-ba5a-4586477fd4ae][Use theme colors in code with modus-themes-with-colors]].
#+findex: modus-themes-get-color-value
@ -3644,7 +3636,7 @@ have lots of extensions, so the "full support" may not be 100% true…
+ csv-mode
+ ctrlf
+ custom (what you get with {{{kbd(M-x customize)}}})
- dashboard [part of {{{development-version}}}]
- dashboard
+ deadgrep
+ deft
+ devdocs

View file

@ -6,7 +6,7 @@
;; 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
;; Version: 4.0.1
;; Version: 4.1.0
;; Package-Requires: ((emacs "27.1"))
;; Keywords: faces, theme, accessibility