elisp-mode is loaded at startup, so the usual methods won't work.
Instead, we tie a transient advice to the emacs-lisp-mode
function, *however*, this function is commonly called by various
packages to parse elisp code! So we have to make sure the emacs lisp
module only initializes the first time it is used interactively.
+ It's too much trouble supporting the evil-org-set-key-theme workflow.
Perhaps I'll make it complain when you do.
+ Don't add +org|setup-ui to doom-load-theme-hook, it's unnecsesary.
+ Use faces in org-priority-faces rather than colors.
Phasing out the +module@name convention for plain old
+module-name-hydra, which is more compatible with elisp reflection tools
like describe-function and such.
Also, Emacs starts up faster now. Tee hee.
Remove +vcs|enable-smerge-mode-maybe, as this is already automatically
enabled when current file is has merge conflicts.
Moved +hydra-smerge to autoloads file, and add it to smerge-mode-hook.
Caused when evil-org-set-key-theme is called too early (somehow).
Also makes evil-org-key-theme customizable, so it doesn't override a
user's changes to it.
Reported by @majorgreys
`set-repl-handler!` helps with opening a repl when a particular mode is
active in a buffer. We want to be able to open a `sly-mrepl` whenever we
are in a lisp buffer, so we should have the repl handler look for
`'lisp-mode` to define opening a sly repl.
I assume the lookup handlers should be making sure we are in a lisp
buffer (similar reasoning to the repl-handler).
Adds support for the saved-wconf window parameter. If a popup possesses
a window configuration in this parameter, it will be restored when the
popup (or its popup buffer) is killed.
This prevents the unnecessary eager-loading of many autodefs (and
evil-collection-elisp-mode), since the elisp-mode package is always
available at startup.
This fixes a keybinding precedence issue that prevented users from
customizing evil-collection's keybinds, because evil-collection would
always run last, *after* user customizations. This precedence problem
occurs because evil-collection was lazy loaded haphazardly.
This isn't the most elegant solution, but I can live with it.
The display function was being set on ivy-display-functions-props. The
correct variable for it is ivy-display-functions-alist.
Reported by randoom in discord.
