This is ef-themes.info, produced by makeinfo version 6.7 from
ef-themes.texi.

Copyright (C) 2022 Free Software Foundation, Inc.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.3 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover Texts
     being “A GNU Manual,” and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     “GNU Free Documentation License.”

     (a) The FSF’s Back-Cover Text is: “You have the freedom to copy and
     modify this GNU manual.”

INFO-DIR-SECTION Emacs misc features
START-INFO-DIR-ENTRY
* Ef-Themes: (ef-themes). Colorful and legible themes.
END-INFO-DIR-ENTRY


File: ef-themes.info,  Node: Top,  Next: Installation,  Up: (dir)

ef-themes: colorful and legible themes
**************************************

Copyright (C) 2022 Free Software Foundation, Inc.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.3 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover Texts
     being “A GNU Manual,” and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     “GNU Free Documentation License.”

     (a) The FSF’s Back-Cover Text is: “You have the freedom to copy and
     modify this GNU manual.”

   This manual, written by Protesilaos Stavrou, describes the Emacs
package called ‘ef-themes’, and provides every other piece of
information pertinent to it.

   The documentation furnished herein corresponds to stable version
0.3.0, released on 2022-08-20.  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 0.4.0-dev.

   • Package name (GNU ELPA): ‘ef-themes’
   • Official manual: <https://protesilaos.com/emacs/ef-themes>
   • Git repo on SourceHut: <https://git.sr.ht/~protesilaos/ef-themes>
        • Mirrors:
             • GitHub: <https://github.com/protesilaos/ef-themes>
             • GitLab: <https://gitlab.com/protesilaos/ef-themes>
   • Mailing list: <https://lists.sr.ht/~protesilaos/ef-themes>

   If you are viewing the README.org version of this file, please note
that the GNU ELPA machinery automatically generates an Info manual out
of it.

* Menu:

* Installation::
* Sample configuration::
* Themes for red-green color deficiency::
* Customization options::
* Loading a theme::
* Commands to load an Ef theme::
* Preview theme colors::
* Use colors from the active Ef theme::
* Do-It-Yourself customizations::
* Supported packages or face groups::
* Principles::
* FAQ::
* Acknowledgements::
* GNU Free Documentation License::
* Indices::

— The Detailed Node Listing —

Installation

* GNU ELPA package::
* Manual installation::

Customization options

* Toggle between two Ef themes::
* Enable mixed fonts::
* UI typeface::
* Option for headings::

Do-It-Yourself customizations

* The general approach to DIY changes::

Supported packages or face groups

* Explicitly supported packages or face groups::
* Implicitly support packages or face groups::
* Packages that are hard to support::

Principles

* Minimal VS maximal scope::

FAQ

* What does Ef mean?::
* Will you stop using the modus-themes?::
* Then why develop the ef-themes?::

Indices

* Function index::
* Variable index::
* Concept index::



File: ef-themes.info,  Node: Installation,  Next: Sample configuration,  Prev: Top,  Up: Top

1 Installation
**************

* Menu:

* GNU ELPA package::
* Manual installation::


File: ef-themes.info,  Node: GNU ELPA package,  Next: Manual installation,  Up: Installation

1.1 GNU ELPA package
====================

The package is available as ‘ef-themes’.  Simply do:

     M-x package-refresh-contents
     M-x package-install

   And search for it.

   GNU ELPA provides the latest stable release.  Those who prefer to
follow the development process in order to report bugs or suggest
changes, can use the version of the package from the GNU-devel ELPA
archive.  Read:
<https://protesilaos.com/codelog/2022-05-13-emacs-elpa-devel/>.


File: ef-themes.info,  Node: Manual installation,  Prev: GNU ELPA package,  Up: Installation

1.2 Manual installation
=======================

Assuming your Emacs files are found in ‘~/.emacs.d/’, execute the
following commands in a shell prompt:

     cd ~/.emacs.d

     # Create a directory for manually-installed packages
     mkdir manual-packages

     # Go to the new directory
     cd manual-packages

     # Clone this repo, naming it "ef-themes"
     git clone https://git.sr.ht/~protesilaos/ef-themes ef-themes

   Finally, in your ‘init.el’ (or equivalent) evaluate this:

     ;; Make Elisp files in that directory available to the user.
     (add-to-list 'load-path "~/.emacs.d/manual-packages/ef-themes")

   Everything is in place to set up the package.


File: ef-themes.info,  Node: Sample configuration,  Next: Themes for red-green color deficiency,  Prev: Installation,  Up: Top

2 Sample configuration
**********************

     (require 'ef-themes)

     ;; If you like two specific themes and want to switch between them, you
     ;; can specify them in `ef-themes-to-toggle' and then invoke the command
     ;; `ef-themes-toggle'.  All the themes are included in the variable
     ;; `ef-themes-collection'.
     (setq ef-themes-to-toggle '(ef-summer ef-winter))

     ;; Make customisations that affect Emacs faces BEFORE loading a theme
     ;; (any change needs a theme re-load to take effect).

     (setq ef-themes-headings ; read the manual's entry or the doc string
           '((0 . (variable-pitch light 1.9))
             (1 . (variable-pitch light 1.8))
             (2 . (variable-pitch regular 1.7))
             (3 . (variable-pitch regular 1.6))
             (4 . (variable-pitch regular 1.5))
             (5 . (variable-pitch 1.4)) ; absence of weight means `bold'
             (6 . (variable-pitch 1.3))
             (7 . (variable-pitch 1.2))
             (t . (variable-pitch 1.1))))

     ;; They are nil by default...
     (setq ef-themes-mixed-fonts t
           ef-themes-variable-pitch-ui t)

     ;; Disable all other themes to avoid awkward blending:
     (mapc #'disable-theme custom-enabled-themes)

     ;; Load the theme of choice:
     (load-theme 'ef-summer :no-confirm)

     ;; The themes we provide:
     ;;
     ;; Light: `ef-day', `ef-light', `ef-spring', `ef-summer'.
     ;; Dark:  `ef-autumn', `ef-dark', `ef-night', `ef-winter'.
     ;;
     ;; Also those which are optimized for deuteranopia (red-green color
     ;; deficiency): `ef-deuteranopia-dark', `ef-deuteranopia-light'.

     ;; We also provide these commands, but do not assign them to any key:
     ;;
     ;; - `ef-themes-toggle'
     ;; - `ef-themes-select'
     ;; - `ef-themes-load-random'
     ;; - `ef-themes-preview-colors'
     ;; - `ef-themes-preview-colors-current'


File: ef-themes.info,  Node: Themes for red-green color deficiency,  Next: Customization options,  Prev: Sample configuration,  Up: Top

3 Themes for red-green color deficiency
***************************************

Most items in the ‘ef-themes’ collection are designed to use colors from
many sides of the spectrum.  Those items generally are inappropriate for
people with red-green color deficiency or deuteranopia.  We do,
nonetheless, provide a light and a dark theme that are optimized for
such users.  The named of the themes are: ‘ef-deuteranopia-dark’ and
‘ef-deuteranopia-light’ (*note Loading a theme::).


File: ef-themes.info,  Node: Customization options,  Next: Loading a theme,  Prev: Themes for red-green color deficiency,  Up: Top

4 Customization options
***********************

The ‘ef-themes’ provide a limited set of user options which tweak
secondary aspects of the theme.  No option affects coloration or the
overall character of each theme (*note Principles::).

   All customizations need to be evaluated before loading a theme.  Any
change thus requires a theme re-load (*note Loading a theme:
Principles.).

* Menu:

* Toggle between two Ef themes::
* Enable mixed fonts::
* UI typeface::
* Option for headings::


File: ef-themes.info,  Node: Toggle between two Ef themes,  Next: Enable mixed fonts,  Up: Customization options

4.1 Toggle between two Ef themes
================================

The user option ‘ef-themes-to-toggle’ expects two symbols that name
items in the Ef themes collection.  The variable ‘ef-themes-collection’
includes a list with all relevant symbols.  The user can then switch
between the two specified themes by invoking the ‘ef-themes-toggle’
command.

   This is in addition to the other ways of loading a theme, either with
minibuffer completion or at random (*note Commands to load an Ef
theme::).


File: ef-themes.info,  Node: Enable mixed fonts,  Next: UI typeface,  Prev: Toggle between two Ef themes,  Up: Customization options

4.2 Enable mixed fonts
======================

[ Part of 0.4.0-dev ]

   The user option ‘ef-themes-mixed-fonts’ controls whether strictly
spacing-sensitive constructs inherit from ‘fixed-pitch’ (a monospaced
font family).

   By default (a nil value for this user option) no face inherits from
‘fixed-pitch’: they all use the default font family, regardless of
whether it is monospaced or not.

   When ‘ef-themes-mixed-fonts’ is set to a non-nil value, faces such as
Org tables, inline code, code blocks, and the like, are rendered in a
monospaced font at all times.  The user can thus set their default font
family to a proportionately spaced font without worrying about breaking
the alignment of relevant elements, or if they simply prefer the
aesthetics of mixed mono and proportionately spaced font families.

   A temporary switch to a proportionately spaced font (known in Emacs
as ‘variable-pitch’) can be enabled in the current buffer with the
activation of the built-in ‘variable-pitch-mode’.

   To get consistent typography, the user may need to edit the font
family of the ‘fixed-pitch’ face.  The ‘fontaine’ package on GNU ELPA
(by Protesilaos) can be helpful in that regard.


File: ef-themes.info,  Node: UI typeface,  Next: Option for headings,  Prev: Enable mixed fonts,  Up: Customization options

4.3 UI typeface
===============

[ Part of 0.4.0-dev ]

   The user option ‘ef-themes-variable-pitch-ui’ controls whether the
elements of the User Interface (UI) use a proportionately spaced font.
By default (a nil value), all UI elements use the default font family.
When this user option is set to a non-nil value, all UI elements will
inherit the face ‘variable-pitch’ instead thus rendering them in a
proportionately spaced font.

   In this context, the UI elements are:

   • ‘header-line’
   • ‘mode-line’ (active and inactive)
   • ‘tab-bar-mode’
   • ‘tab-line-mode’

   To get consistent typography, the user may need to edit the font
family of the ‘variable-pitch’ face.  The ‘fontaine’ package on GNU ELPA
(by Protesilaos) can be helpful in that regard.


File: ef-themes.info,  Node: Option for headings,  Prev: UI typeface,  Up: Customization options

4.4 Option for headings
=======================

The user option ‘ef-themes-headings’ provides support for individual
heading styles for levels 0 through 8.

   This is an alist that accepts a ‘(key . list-of-values)’ combination.
The key is either a number, representing the heading’s level (0 through
8) or ‘t’, which pertains to the fallback style.

   Level 0 is a special heading: it is used for what counts as a
document title or equivalent, such as the ‘#+title’ construct we find in
Org files.  Levels 1-8 are regular headings.

   The list of values covers symbols that refer to properties, as
described below.  Here is a complete sample, followed by a presentation
of all available properties:

     (setq ef-themes-headings
           '((1 . (light variable-pitch 1.5))
             (2 . (regular 1.3))
             (3 . (1.1))
             (t . (variable-pitch))))

   By default (a ‘nil’ value for this variable), all headings have a
bold typographic weight, a font family that is the same as the ‘default’
face (typically monospaced), and a height that is equal to the ‘default’
face’s height.

   • A ‘variable-pitch’ property changes the font family of the heading
     to that of the ‘variable-pitch’ face (normally a proportionately
     spaced typeface).  Also check the ‘fontaine’ package (by
     Protesilaos) for tweaking fonts via faces.

   • The symbol of a weight attribute adjusts the font of the heading
     accordingly, such as ‘light’, ‘semibold’, etc.  Valid symbols are
     defined in the variable ‘ef-themes-weights’.  The absence of a
     weight means that bold will be used by virtue of inheriting the
     ‘bold’ face.

   • A number, expressed as a floating point (e.g.  1.5), adjusts the
     height of the heading to that many times the base font size.  The
     default height is the same as 1.0, though it need not be explicitly
     stated.  Instead of a floating point, an acceptable value can be in
     the form of a cons cell like ‘(height . FLOAT)’ or ‘(height
     FLOAT)’, where ‘FLOAT’ is the given number.

   Combinations of any of those properties are expressed as a list, like
in these examples:

     (semibold)
     (variable-pitch semibold)
     (variable-pitch semibold 1.3)
     (variable-pitch semibold (height 1.3))   ; same as above
     (variable-pitch semibold (height . 1.3)) ; same as above

   The order in which the properties are set is not significant.

   In user configuration files the form may look like this:

     (setq ef-themes-headings
           '((1 . (light variable-pitch 1.5))
             (2 . (regular 1.3))
             (3 . (1.1))
             (t . (variable-pitch))))

   When defining the styles per heading level, it is possible to pass a
non-nil value (t) instead of a list of properties.  This will retain the
original aesthetic for that level.  For example:

     (setq ef-themes-headings
           '((1 . t)           ; keep the default style
             (2 . (variable-pitch 1.2))
             (t . (variable-pitch)))) ; style for all other headings

     (setq ef-themes-headings
           '((1 . (variable-pitch 1.6))
             (2 . (1.3))
             (t . t))) ; default style for all other levels


File: ef-themes.info,  Node: Loading a theme,  Next: Commands to load an Ef theme,  Prev: Customization options,  Up: Top

5 Loading a theme
*****************

Emacs can load and maintain enabled multiple themes at once.  This
typically leads to awkward styling and weird combinations.  The theme
looks broken and the designer’s intent is misunderstood.  Before loading
one of the ‘ef-themes’, the user is encouraged to disable all others:

     (mapc #'disable-theme custom-enabled-themes)

   Then load the theme of choice.  For example:

     (load-theme 'ef-summer :no-confirm)

   The ‘:no-confirm’ is optional.  It simply skips the step where Emacs
asks the user whether they are sure about loading the theme.

   Consider adding code like the above to the user configuration file,
such as ‘init.el’.


File: ef-themes.info,  Node: Commands to load an Ef theme,  Next: Preview theme colors,  Prev: Loading a theme,  Up: Top

6 Commands to load an Ef theme
******************************

The commands mentioned herein call ‘ef-themes-post-load-hook’ at the
end.  This is for advanced users who want to trigger some code after an
Ef theme is loaded (*note Use colors from the active Ef theme::).  The
same goes for ‘ef-themes-toggle’ (*note Toggle between two Ef themes::).

   The themes can also be loaded interactively (*note Loading a
theme::).  The command ‘ef-themes-select’ (call it with ‘M-x’) prompts
with minibuffer completion for a theme among the collection of items we
provide.  It then loads the selected theme.  Internally,
‘ef-themes-select’ takes care to disable any other Ef theme, though it
does not disable other themes.  This is by design to let users maintain
theme blending when they want it.  Otherwise, the user is encouraged to
disable all other themes and stick with the Ef themes:

     (mapc #'disable-theme custom-enabled-themes)

   The command ‘ef-themes-load-random’ is for those who appreciate a bit
of serendipity in their life.  When call interactively with ‘M-x’ it
loads a random theme from the Ef themes collection.  The selection
excludes the current Ef theme.  Calling ‘ef-themes-load-random’ with a
prefix argument (‘C-u’ by default) makes the command limit the random
selection to either light or dark themes.  The user is prompted with
minibuffer completion to pick among the two sets.

   The ‘ef-themes-load-random’ can also be called from Lisp (e.g.  from
the ‘init.el’ file):

     (ef-themes-load-random)

   This has the effect of loading an Ef theme at random, as described
above.  It is also possible to limit the set with either of those:

     ;; Load a light Ef theme at random
     (ef-themes-load-random 'light)

     ;; Load a dark Ef theme at random
     (ef-themes-load-random 'dark)

   The author of the Ef themes likes to check with their operating
system to determine if the desktop environment outside of Emacs is using
a light/dark theme and then loads an appropriate Ef theme at random:

     ;; Check GNOME's gsettings database for the dark theme preference.  If
     ;; it is enabled, we want to load a dark Ef theme at random.  Otherwise
     ;; we load a random light theme.
     (if (string-match-p
          "dark"
          (shell-command-to-string "gsettings get org.gnome.desktop.interface color-scheme"))
         (ef-themes-load-random 'dark)
       (ef-themes-load-random 'light))


File: ef-themes.info,  Node: Preview theme colors,  Next: Use colors from the active Ef theme,  Prev: Commands to load an Ef theme,  Up: Top

7 Preview theme colors
**********************

The command ‘ef-themes-preview-colors’ uses minibuffer completion to
select an item from the Ef themes and then produces a buffer with
previews of its color palette entries.  The buffer has a naming scheme
which reflects the given choice, like ‘ef-summer-preview-colors’ for the
‘ef-summer’ theme.

   The command ‘ef-themes-preview-colors-current’ skips the minibuffer
selection process and just produces a preview for the current Ef theme.


File: ef-themes.info,  Node: Use colors from the active Ef theme,  Next: Do-It-Yourself customizations,  Prev: Preview theme colors,  Up: Top

8 Use colors from the active Ef theme
*************************************

Advanced users may want to call color variables from the palette of the
active Ef theme.  The macro ‘ef-themes-with-colors’ supplies those to
any form called inside of it.  For example:

     (ef-themes-with-colors
       (list bg-main fg-main bg-mode-line cursor))
     ;; => ("#fff2f3" "#5f456f" "#ffa4dc" "#cf0090")

   The above return value is for ‘ef-summer’ when that is the active Ef
theme.  Switching to another theme and evaluating this code anew will
give us the relevant results for that theme.  The same with ‘ef-winter’:

     (ef-themes-with-colors
       (list bg-main fg-main bg-mode-line cursor))
     ;; => ("#0f0b15" "#b8c6d5" "#5f1f5f" "#ff6ff0")

   *note Do-It-Yourself customizations::.

   The palette of each Ef theme is considered stable.  No removals shall
be made.  Though please note that some tweaks to individual hues or
color mapping are still possible.  At any rate, we will not outright
break any code that uses ‘ef-themes-with-colors’.


File: ef-themes.info,  Node: Do-It-Yourself customizations,  Next: Supported packages or face groups,  Prev: Use colors from the active Ef theme,  Up: Top

9 Do-It-Yourself customizations
*******************************

This section documents how the user can further tweak the Ef themes to
their liking.

* Menu:

* The general approach to DIY changes::


File: ef-themes.info,  Node: The general approach to DIY changes,  Up: Do-It-Yourself customizations

9.1 The general approach to DIY changes
=======================================

When the user wants to customize Emacs faces there are two
considerations they need to make if they care about robustness:

  1. Do not hardcode color values, but instead use the relevant
     variables from the Ef themes.
  2. Make the changes persist through theme changes between the Ef
     themes collection.

   For point 1 we provide the ‘ef-themes-with-colors’ macro, while for
point 2 we have the ‘ef-themes-post-load-hook’.

   *note Use colors from the active Ef theme::.

   *note Commands to load an Ef theme::.

   We need to wrap our code in the ‘ef-themes-with-colors’ and declare
it as a function which we then add to the hook.  Here we show the
general approach of putting those pieces together.

   To customize faces we use the built-in ‘custom-set-faces’.  The value
it accepts has the same syntax as that found in ‘ef-themes.el’,
specifically the ‘ef-themes-faces’ constant.  It thus is easy to copy
lines from there and tweak them.  Let’s pick a couple of font-lock faces
(used in all programming modes, among others):

     (defun my-ef-themes-custom-faces ()
       "My customizations on top of the Ef themes.
     This function is added to the `ef-themes-post-load-hook'."
       (ef-themes-with-colors
         (custom-set-faces
          ;; These are the default specifications
          `(font-lock-comment-face ((,c :inherit italic :foreground ,comment)))
          `(font-lock-variable-name-face ((,c :foreground ,variable))))))

     ;; Using the hook lets our changes persist when we use the commands
     ;; `ef-themes-toggle', `ef-themes-select', and `ef-themes-load-random'.
     (add-hook 'ef-themes-post-load-hook #'my-ef-themes-custom-faces)

   Each item in the Ef themes collection has its own color mapping.  So
the color value of the ‘comment’ variable will differ from
theme-to-theme.  For our purposes, we make variables look like comments
and comments like variables:

     (defun my-ef-themes-custom-faces ()
       "My customizations on top of the Ef themes.
     This function is added to the `ef-themes-post-load-hook'."
       (ef-themes-with-colors
         (custom-set-faces
          ;; These are the default specifications
          `(font-lock-comment-face ((,c :foreground ,variable)))
          `(font-lock-variable-name-face ((,c :inherit italic :foreground ,comment))))))

     ;; Using the hook lets our changes persist when we use the commands
     ;; `ef-themes-toggle', `ef-themes-select', and `ef-themes-load-random'.
     (add-hook 'ef-themes-post-load-hook #'my-ef-themes-custom-faces)

   All changes take effect when a theme is loaded again.

   Please contact us if you have specific questions about this
mechanism.  We are willing to help and shall provide comprehensive
documentation where necessary.


File: ef-themes.info,  Node: Supported packages or face groups,  Next: Principles,  Prev: Do-It-Yourself customizations,  Up: Top

10 Supported packages or face groups
************************************

The ‘ef-themes’ will only ever support a curated list of packages based
on my judgement (*note Packages that are hard to support::).
Nevertheless, the list of explicitly or implicitly supported packages
already covers everything most users need.

* Menu:

* Explicitly supported packages or face groups::
* Implicitly support packages or face groups::
* Packages that are hard to support::


File: ef-themes.info,  Node: Explicitly supported packages or face groups,  Next: Implicitly support packages or face groups,  Up: Supported packages or face groups

10.1 Explicitly supported packages or face groups
=================================================

   • all basic faces
   • all-the-icons
   • all-the-icons-dired
   • all-the-icons-ibuffer
   • ansi-color
   • bongo
   • bookmark
   • calendar and diary
   • change-log and log-view (part of VC)
   • chart
   • compilation
   • completions
   • custom (M-x customize)
   • denote
   • dictionary
   • diff-hl
   • diff-mode
   • dired
   • dired-subtree
   • diredfl
   • doom-modeline (incomplete, though likely is okay)
   • ediff
   • eldoc
   • elfeed
   • epa
   • eshell
   • eww [ Part of 0.4.0-dev ]
   • font-lock
   • git-commit
   • git-rebase
   • gnus (incomplete, though likely is okay)
   • info
   • isearch, occur, query-replace
   • keycast
   • line numbers (‘display-line-numbers-mode’ and global variant)
   • magit
   • man
   • marginalia
   • markdown-mode
   • messages
   • mode-line
   • mu4e
   • notmuch
   • orderless
   • org
   • org-habit
   • org-modern
   • outline-mode
   • outline-minor-faces
   • package (M-x list-packages)
   • rainbow-delimiters
   • rcirc
   • regexp-builder (re-builder)
   • ruler-mode
   • shell-script-mode (sh-mode)
   • show-paren-mode
   • shr [ Part of 0.4.0-dev ]
   • smerge
   • tab-bar-mode
   • tab-line-mode
   • term
   • textsec
   • transient
   • vc (‘vc-dir.el’, ‘vc-hooks.el’)
   • vertico
   • wgrep
   • which-function-mode
   • whitespace-mode
   • widget
   • woman


File: ef-themes.info,  Node: Implicitly support packages or face groups,  Next: Packages that are hard to support,  Prev: Explicitly supported packages or face groups,  Up: Supported packages or face groups

10.2 Implicitly support packages or face groups
===============================================

Those are known to work with the Ef themes either because their colors
are appropriate or because they inherit from basic faces which the
themes already cover:

   • apropos
   • consult
   • corfu
   • dim-autoload
   • embark
   • flycheck
   • flymake
   • flyspell
   • hl-todo
   • icomplete
   • ido
   • lin
   • multiple-cursors
   • paren-face
   • pulsar
   • tempel
   • which-key (seems okay, but may need explicit support)
   • xref


File: ef-themes.info,  Node: Packages that are hard to support,  Prev: Implicitly support packages or face groups,  Up: Supported packages or face groups

10.3 Packages that are hard to support
======================================

These are difficult to support due to their (i) incompatibility with the
design of the ‘ef-themes’, (ii) complexity or multitude of points of
entry, (iii) external dependencies, (iv) existence of better
alternatives in my opinion, or (v) inconsiderate use of color
out-of-the-box and implicit unwillingness to be good Emacs citizens:

auctex
     it has a zillion dependencies; I don’t know LaTeX.

avy
     its UI is prone to visual breakage and is hard to style correctly.

calibredb
     has an external dependency that I don’t use.

ctrlf
     use the built-in isearch or the ‘consult-line’ command of
     ‘consult’.

dired+
     it is complex and makes inconsiderate use of color.

ein (Emacs IPython Notebook)
     external dependency that I don’t use.

elfeed-goodies
     depends on ‘powerline’...

ement.el :: has an external dependency that I don’t use. - helm
     it is complex and makes inconsiderate use of color.  Prefer the
     ‘vertico’, ‘consult’, and ‘embark’ packages.

info+
     it is complex and makes inconsiderate use of color.

ivy/counsel/swiper
     use the ‘vertico’, ‘consult’, and ‘embark’ packages which are
     designed to be compatible with standard Emacs mechanisms and are
     modular.

lsp-mode
     has external dependencies that I don’t use.

powerline
     requires too many shades of background and generally violates our
     expectation of how the mode-line is supposed to look by placing the
     designated default background in unexpected places.

selectrum
     use ‘vertico’.

solaire
     in principle, it is incompatible with practically every theme that
     is not designed around it.  Emacs does not distinguish between “UI”
     and “syntax” buffers.

spaceline
     same as ‘powerline’.

sx
     has an external dependency that I don’t use.

telega
     has an external dependency that I don’t use (I don’t even have a
     smartphone).

telephone-line
     same as ‘powerline’.

treemacs
     it has too many dependencies and does too many things.

web-mode
     I don’t use all those Web technologies and cannot test this
     properly without support from an expert.

   The above list is non-exhaustive though you get the idea.


File: ef-themes.info,  Node: Principles,  Next: FAQ,  Prev: Supported packages or face groups,  Up: Top

11 Principles
*************

   • No customization options that affect the coloration of individual
     components !  Either you like them or you don’t.  To change faces,
     it is better to do it in user-level configurations (report the
     issue and we can help with the relevant code).  Providing
     customizations that refashion a wide set of themes is not
     maintainable.

   • Curated list of supported faces (*note Supported packages or face
     groups::).  I will only cover what I use and/or know is in a
     well-maintained state.  Styling a package requires a lot of work as
     one must (i) know how the package works, (ii) see all its
     interfaces in action, (iii) make sure that the color combinations
     look consistent with the rest of the theme.

   • Minimum contrast ratio of 4.5:1 against the main background (WCAG
     AA standard).  Use my ‘modus-themes’ package (also built into Emacs
     28 or higher) if you need top-class accessibility.

* Menu:

* Minimal VS maximal scope::


File: ef-themes.info,  Node: Minimal VS maximal scope,  Up: Principles

11.1 Minimal VS maximal scope
=============================

The ‘ef-themes’ are meant to be minimal in scope, as opposed to my
‘modus-themes’ whose accessibility requirements make them maximalist by
necessity.  The ‘modus-themes’ are such because:

  1. Accessibility is not a one-size-fits-all.  Customisation options
     are necessary to empower users.
  2. Accessibility is as good as its weakest link.  If the user spends
     all day using FOO package, it needs to be perfectly legible,
     otherwise the whole theme fails to deliver on its promise.

   The ‘ef-themes’ can afford to be minimal because they do not have
such a lofty accessibility target.


File: ef-themes.info,  Node: FAQ,  Next: Acknowledgements,  Prev: Principles,  Up: Top

12 FAQ
******

* Menu:

* What does Ef mean?::
* Will you stop using the modus-themes?::
* Then why develop the ef-themes?::


File: ef-themes.info,  Node: What does Ef mean?,  Next: Will you stop using the modus-themes?,  Up: FAQ

12.1 What does Ef mean?
=======================

“Ef” is a Greek word (ευ), commonly used as a prefix to denote that
something is good, nice, and/or easy.  For example, eftopia (ευτοπία) is
the opposite of dystopia (δυστοπία): a good place as opposed to a bad
place.


File: ef-themes.info,  Node: Will you stop using the modus-themes?,  Next: Then why develop the ef-themes?,  Prev: What does Ef mean?,  Up: FAQ

12.2 Will you stop using the modus-themes?
==========================================

No.  For my workflow, accessibility is the most important quality.  The
‘modus-themes’ will remain my default choice.


File: ef-themes.info,  Node: Then why develop the ef-themes?,  Prev: Will you stop using the modus-themes?,  Up: FAQ

12.3 Then why develop the ef-themes?
====================================

Because I think that users deserve “pretty” themes that (i) do make some
considerations for legibility, and (ii) are not designed on a whimsy.

   The ‘ef-themes’ are my answer to those who (i) like my
‘modus-themes’, (ii) want something with a bit more flair, and (iii) are
fine with a bit more relaxed accessibility target.


File: ef-themes.info,  Node: Acknowledgements,  Next: GNU Free Documentation License,  Prev: FAQ,  Up: Top

13 Acknowledgements
*******************

This project is meant to be a collective effort.  Every bit of help
matters.

Author/maintainer
     Protesilaos Stavrou.

Contributions to code or the manual
     Philip Kaludercic.

Ideas and/or user feedback
     Anthony Chavez, Iris Garcia, Jean-Philippe Gagné Guay, Spike-Leung,
     Summer Emacs, Zoltán Király.


File: ef-themes.info,  Node: GNU Free Documentation License,  Next: Indices,  Prev: Acknowledgements,  Up: Top

14 GNU Free Documentation License
*********************************

                     Version 1.3, 3 November 2008

     Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
     <https://fsf.org/>

     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.

  0. PREAMBLE

     The purpose of this License is to make a manual, textbook, or other
     functional and useful document “free” in the sense of freedom: to
     assure everyone the effective freedom to copy and redistribute it,
     with or without modifying it, either commercially or
     noncommercially.  Secondarily, this License preserves for the
     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
     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.

     We have designed this License in order to use it for manuals for
     free software, because free software needs free documentation: a
     free program should come with manuals providing the same freedoms
     that the software does.  But this License is not limited to
     software manuals; it can be used for any textual work, regardless
     of subject matter or whether it is published as a printed book.  We
     recommend this License principally for works whose purpose is
     instruction or reference.

  1. APPLICABILITY AND DEFINITIONS

     This License applies to any manual or other work, in any medium,
     that contains a notice placed by the copyright holder saying it can
     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
     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
     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
     of the Document that deals exclusively with the relationship of the
     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
     explain any mathematics.)  The relationship could be a matter of
     historical connection with the subject or with related matters, or
     of legal, commercial, philosophical, ethical or political position
     regarding them.

     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
     is not allowed to be designated as Invariant.  The Document may
     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
     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,
     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
     of pixels) generic paint programs or (for drawings) some widely
     available drawing editor, and that is suitable for input to text
     formatters or for automatic translation to a variety of formats
     suitable for input to text formatters.  A copy made in an otherwise
     Transparent file format whose markup, or absence of markup, has
     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”.

     Examples of suitable formats for Transparent copies include plain
     ASCII without markup, Texinfo input format, LaTeX input format,
     SGML or XML using a publicly available DTD, and standard-conforming
     simple HTML, PostScript or PDF designed for human modification.
     Examples of transparent image formats include PNG, XCF and JPG.
     Opaque formats include proprietary formats that can be read and
     edited only by proprietary word processors, SGML or XML for which
     the DTD and/or processing tools are not generally available, and
     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,
     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.

     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
     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
     to this definition.

     The Document may include Warranty Disclaimers next to the notice
     which states that this License applies to the Document.  These
     Warranty Disclaimers are considered to be included by reference in
     this License, but only as regards disclaiming warranties: any other
     implication that these Warranty Disclaimers may have is void and
     has no effect on the meaning of this License.

  2. VERBATIM COPYING

     You may copy and distribute the Document in any medium, either
     commercially or noncommercially, provided that this License, the
     copyright notices, and the license notice saying this License
     applies to the Document are reproduced in all copies, and that you
     add no other conditions whatsoever to those of this License.  You
     may not use technical measures to obstruct or control the reading
     or further copying of the copies you make or distribute.  However,
     you may accept compensation in exchange for copies.  If you
     distribute a large enough number of copies you must also follow the
     conditions in section 3.

     You may also lend copies, under the same conditions stated above,
     and you may publicly display copies.

  3. COPYING IN QUANTITY

     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
     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
     and legibly identify you as the publisher of these copies.  The
     front cover must present the full title with all words of the title
     equally prominent and visible.  You may add other material on the
     covers in addition.  Copying with changes limited to the covers, as
     long as they preserve the title of the Document and satisfy these
     conditions, can be treated as verbatim copying in other respects.

     If the required texts for either cover are too voluminous to fit
     legibly, you should put the first ones listed (as many as fit
     reasonably) on the actual cover, and continue the rest onto
     adjacent pages.

     If you publish or distribute Opaque copies of the Document
     numbering more than 100, you must either include a machine-readable
     Transparent copy along with each Opaque copy, or state in or with
     each Opaque copy a computer-network location from which the general
     network-using public has access to download using public-standard
     network protocols a complete Transparent copy of the Document, free
     of added material.  If you use the latter option, you must take
     reasonably prudent steps, when you begin distribution of Opaque
     copies in quantity, to ensure that this Transparent copy will
     remain thus accessible at the stated location until at least one
     year after the last time you distribute an Opaque copy (directly or
     through your agents or retailers) of that edition to the public.

     It is requested, but not required, that you contact the authors of
     the Document well before redistributing any large number of copies,
     to give them a chance to provide you with an updated version of the
     Document.

  4. MODIFICATIONS

     You may copy and distribute a Modified Version of the Document
     under the conditions of sections 2 and 3 above, provided that you
     release the Modified Version under precisely this License, with the
     Modified Version filling the role of the Document, thus licensing
     distribution and modification of the Modified Version to whoever
     possesses a copy of it.  In addition, you must do these things in
     the Modified Version:

       A. Use in the Title Page (and on the covers, if any) a title
          distinct from that of the Document, and from those of previous
          versions (which should, if there were any, be listed in the
          History section of the Document).  You may use the same title
          as a previous version if the original publisher of that
          version gives permission.

       B. List on the Title Page, as authors, one or more persons or
          entities responsible for authorship of the modifications in
          the Modified Version, together with at least five of the
          principal authors of the Document (all of its principal
          authors, if it has fewer than five), unless they release you
          from this requirement.

       C. State on the Title page the name of the publisher of the
          Modified Version, as the publisher.

       D. Preserve all the copyright notices of the Document.

       E. Add an appropriate copyright notice for your modifications
          adjacent to the other copyright notices.

       F. Include, immediately after the copyright notices, a license
          notice giving the public permission to use the Modified
          Version under the terms of this License, in the form shown in
          the Addendum below.

       G. Preserve in that license notice the full lists of Invariant
          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,
          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
          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
          previous sentence.

       J. Preserve the network location, if any, given in the Document
          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
          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”,
          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.

       L. Preserve all the Invariant Sections of the Document, unaltered
          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
          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
          Section.

       O. Preserve any Warranty Disclaimers.

     If the Modified Version includes new front-matter sections or
     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
     license notice.  These titles must be distinct from any other
     section titles.

     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.

     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
     the list of Cover Texts in the Modified Version.  Only one passage
     of Front-Cover Text and one of Back-Cover Text may be added by (or
     through arrangements made by) any one entity.  If the Document
     already includes a cover text for the same cover, previously added
     by you or by arrangement made by the same entity you are acting on
     behalf of, you may not add another; but you may replace the old
     one, on explicit permission from the previous publisher that added
     the old one.

     The author(s) and publisher(s) of the Document do not by this
     License give permission to use their names for publicity for or to
     assert or imply endorsement of any Modified Version.

  5. COMBINING DOCUMENTS

     You may combine the Document with other documents released under
     this License, under the terms defined in section 4 above for
     modified versions, provided that you include in the combination all
     of the Invariant Sections of all of the original documents,
     unmodified, and list them all as Invariant Sections of your
     combined work in its license notice, and that you preserve all
     their Warranty Disclaimers.

     The combined work need only contain one copy of this License, and
     multiple identical Invariant Sections may be replaced with a single
     copy.  If there are multiple Invariant Sections with the same name
     but different contents, make the title of each such section unique
     by adding at the end of it, in parentheses, the name of the
     original author or publisher of that section if known, or else a
     unique number.  Make the same adjustment to the section titles in
     the list of Invariant Sections in the license notice of the
     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.”

  6. COLLECTIONS OF DOCUMENTS

     You may make a collection consisting of the Document and other
     documents released under this License, and replace the individual
     copies of this License in the various documents with a single copy
     that is included in the collection, provided that you follow the
     rules of this License for verbatim copying of each of the documents
     in all other respects.

     You may extract a single document from such a collection, and
     distribute it individually under this License, provided you insert
     a copy of this License into the extracted document, and follow this
     License in all other respects regarding verbatim copying of that
     document.

  7. AGGREGATION WITH INDEPENDENT WORKS

     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
     copyright resulting from the compilation is not used to limit the
     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
     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
     the whole aggregate.

  8. TRANSLATION

     Translation is considered a kind of modification, so you may
     distribute translations of the Document under the terms of section
     4.  Replacing Invariant Sections with translations requires special
     permission from their copyright holders, but you may include
     translations of some or all Invariant Sections in addition to the
     original versions of these Invariant Sections.  You may include a
     translation of this License, and all the license notices in the
     Document, and any Warranty Disclaimers, provided that you also
     include the original English version of this License and the
     original versions of those notices and disclaimers.  In case of a
     disagreement between the translation and the original version of
     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
     Preserve its Title (section 1) will typically require changing the
     actual title.

  9. TERMINATION

     You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided under this License.  Any attempt
     otherwise to copy, modify, sublicense, or distribute it is void,
     and will automatically terminate your rights under this License.

     However, if you cease all violation of this License, then your
     license from a particular copyright holder is reinstated (a)
     provisionally, unless and until the copyright holder explicitly and
     finally terminates your license, and (b) permanently, if the
     copyright holder fails to notify you of the violation by some
     reasonable means prior to 60 days after the cessation.

     Moreover, your license from a particular copyright holder is
     reinstated permanently if the copyright holder notifies you of the
     violation by some reasonable means, this is the first time you have
     received notice of violation of this License (for any work) from
     that copyright holder, and you cure the violation prior to 30 days
     after your receipt of the notice.

     Termination of your rights under this section does not terminate
     the licenses of parties who have received copies or rights from you
     under this License.  If your rights have been terminated and not
     permanently reinstated, receipt of a copy of some or all of the
     same material does not give you any rights to use it.

  10. FUTURE REVISIONS OF THIS LICENSE

     The Free Software Foundation may publish new, revised versions of
     the GNU Free Documentation License from time to time.  Such new
     versions will be similar in spirit to the present version, but may
     differ in detail to address new problems or concerns.  See
     <https://www.gnu.org/licenses/>.

     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
     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
     Document does not specify a version number of this License, you may
     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
     authorizes you to choose that version for the Document.

  11. RELICENSING

     “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
     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
     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
     in part, as part of another Document.

     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
     texts or invariant sections, and (2) were thus incorporated prior
     to November 1, 2008.

     The operator of an MMC Site may republish an MMC contained in the
     site under CC-BY-SA on the same site at any time before August 1,
     2009, provided the MMC is eligible for relicensing.

ADDENDUM: How to use this License for your documents
====================================================

To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and license
notices just after the title page:

       Copyright (C)  YEAR  YOUR NAME.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.3
       or any later version published by the Free Software Foundation;
       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
       Texts.  A copy of the license is included in the section entitled ``GNU
       Free Documentation License''.

   If you have Invariant Sections, Front-Cover Texts and Back-Cover
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
         being LIST.

   If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.

   If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of free
software license, such as the GNU General Public License, to permit
their use in free software.


File: ef-themes.info,  Node: Indices,  Prev: GNU Free Documentation License,  Up: Top

15 Indices
**********

* Menu:

* Function index::
* Variable index::
* Concept index::


File: ef-themes.info,  Node: Function index,  Next: Variable index,  Up: Indices

15.1 Function index
===================


File: ef-themes.info,  Node: Variable index,  Next: Concept index,  Prev: Function index,  Up: Indices

15.2 Variable index
===================


File: ef-themes.info,  Node: Concept index,  Prev: Variable index,  Up: Indices

15.3 Concept index
==================



Tag Table:
Node: Top835
Node: Installation3672
Node: GNU ELPA package3854
Node: Manual installation4418
Node: Sample configuration5199
Node: Themes for red-green color deficiency7236
Node: Customization options7868
Node: Toggle between two Ef themes8499
Node: Enable mixed fonts9130
Node: UI typeface10490
Node: Option for headings11424
Node: Loading a theme14810
Node: Commands to load an Ef theme15634
Node: Preview theme colors18237
Node: Use colors from the active Ef theme18887
Node: Do-It-Yourself customizations20098
Node: The general approach to DIY changes20457
Node: Supported packages or face groups23446
Node: Explicitly supported packages or face groups24049
Node: Implicitly support packages or face groups25825
Node: Packages that are hard to support26615
Node: Principles29121
Node: Minimal VS maximal scope30260
Node: FAQ31014
Node: What does Ef mean?31230
Node: Will you stop using the modus-themes?31626
Node: Then why develop the ef-themes?31983
Node: Acknowledgements32517
Node: GNU Free Documentation License32990
Node: Indices58335
Node: Function index58513
Node: Variable index58638
Node: Concept index58785

End Tag Table


Local Variables:
coding: utf-8
End:
