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.
* 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
The popup manager (by default) auto-kills most popup buffers after
~5s (controlled by the :ttl property). However, when backtrace buffers
are killed, it calls `top-level`. When the popup manager kills the
buffer, this causes janky cursor movement and the message "Back to top
level" to be displayed in the minibuffer.
Buffers have no read syntax and cannot be serialized. This would cause
errors when :ui workspaces users try to restore sessions that contained
buffer lists.
Fixes an issue where dtrt-indent and/or nav-flash would hang Emacs when
opening large files, and disables all mode hooks for large
files (without using fundamental-mode so you can at least get syntax
highlighting).
SPC u SPC TAB d will prompt you for the workspace you want to delete,
with the name of the current workspace prefilled into the the
minibuffer. This filters out all other workspaces from the get go, which
may fool you into thinking you can only delete the current workspace.
Now it only selects the current workspace by default, without filtering
them.
A change upstream causes the prompt to be suppressed if the current
command wasn't run interactively. The check for interactivity gets
tricky when advice are involved.
