If lexical-binding isn't enabled (with ';; -*- lexical-binding: t; -*-'
at the top of your private config), custom-set-theme! and
custom-theme-set-faces! throw this error. Since these macros are
commonly used in user configs, where I can't police lexical-binding,
I've refactored it to not rely on it.
- doom/increase-font-size no longer resets the font when resizing back
to 0 (causing an inelegant flash of the frame).
- doom/reset-font-size will now reset text-scale, as well, if it is
being used.
- doom/*-font-size commands have been changed to only affect the current
frame.
- doom-big-font-mode will now affect all frames (since minor modes can't
be frame-local).
Keybinds that correct behavior or provide or extend vim functionality
were moved to their respective modules, or to the :editor evil module.
Keybinds in the global space, that are particularly opinionated but
potentially harmful or imposing as a default, or likely for users to
change (like leader keys), are kept in config/default.
email/notmuch: general improvements
- Filter read messages in notmuch show (by folding them automatically)
- Refresh all notmuch buffers after sync (via process sentinel)
- Support custom sync commands (introduces an additional defvar)
- Add command to select From email prior to composing via ivy
There are a few workflows where having multiple buffers (e.g.
side-by-side) is preferrable, however, `dired-find-alternate-file` kills
the old buffer indiscriminately.
* Add an FAQ action to doom-dashboard
* Separate faq and user manual
This is necessary until I can dispatch properly the (file-exists-p)
conditions in the :action part of the variable.
The issue is that the value in :action needs to be a symbol (symbolp)
and the (if COND THEN ELSE) form does not match this.
* Use doom/help-search if (or faq.org manual.org)
Since the function searches through the (in-progress) manual and faq
* Remove :when condition from Search Documentation
This condition is unnecessary since doom/help-search now always at least
lists the modules from doom/help-modules
Now, inline evaluation will display results in an overlay next to the
cursor, rather than in the minibuffer (unless it gets too big, in which
case it'll use a popup buffer).
