When evil-escape is invoked from multiedit-insert state, it erroneously
quits the current multiedit session entirely. No more.
This can be removed when syl20bnr/evil-escape#83 is merged.
+ Don't clear yas-minor-mode-map; the default keybinds can be useful,
esp to non-evil users.
+ Moved +snippets|enable-project-modes hook to autoloads file.
+ Reformat yasnippet config.
+ :sh can now be fed commands to run immediately, e.g. :sh cd %:P to
start from the current project root.
+ Eshell will spawn a new eshell on every split. This can be controlled
via `+eshell-enable-new-shell-on-split'
+ Eshell can be configured to kill the window when you kill the eshell
process. This is disabled by default. See
`+eshell-kill-window-on-exit'. Some commands ignore this, like the
quit-and-close command (I alias this to "q").
+ eshell-directory-name has been moved to doom-etc-dir/eshell. It will
seem like eshell has forgotten all your history, but you can move
~/.eshell (or ~/.doom.d/eshell) to ~/.emacs.d/.local/etc/eshell and
you'll be fine.
+ eshell-aliases-file has been moved to ~/.doom.d/eshell_aliases by
default.
+ Automatic writing to eshell-aliases-file has been disabled. No shell
so aggressively persists aliases. You may maintain it yourself, or use
the new +eshell-aliases variable to customize eshell from Doom.
+ C-s now invokes a history search with ivy/helm.
+ C-c s and C-c v split horizontally and vertically. Inspired by tmux.
+ C-c x kill the current eshell and its window. Inspired by tmux.j
+ New set-eshell-alias! autodef for defining your own aliases.
+ +eshell/open-workspace has been replaced with +eshell/open-fullscreen.
+ Added the "cd-to-project" command. I suggest you alias it.
Stubs are defined as ordinary macros (with defmacro), but if an autodef
is defined with cl-defun, defmacro can't handle the clisp-style argument
lists, causing wrong-number-of-arguments errors.
The error handlers were a little too effective. They obscured a large
chunk of the stacktrace after errors, even in debug mode. This fixes
that and ensures backtraces in debug mode are more helpful.
This fix prevented the byte-compiler from trying to load packages that
were disabled or failed their :when/:unless/:if predicates. This commit
moves it into doom-byte-compile, so the :no-require predicate doesn't
have to run on every package in an interactive session, eating MY
PRECIOUS cpu cycles.
I do love my cpu cycles, yessiree.
This will hopefully reveal more information as to the cause and origin
of errors at startup. It should also make doom-debug-mode more likely to
produce a backtrace in non-interactive sessions.
Now accepts a flat plist of all its former parameters, including new
:parameters and :actions properties to increase your control over the
fate of your windows.
The old usage of set-popup-rule! is deprecated and may not work right!
The :ui popup module has also seen a major refactor to improve
efficiency and load times.
Sorry! This is the last "big" change before 2.1!
This naming convention was meant to be for batch commands, but it grew
to include "commands that were helpful with managing Doom", but many of
these commands shouldn't be interactive in the first place!
