problem:
some layer packages lists have the open and closing parentheses on the same line
as the first and last listed package, but most seem to have them on a separate
lines.
solution:
put the open and close parentheses on separate lines, except for lists with only
a single package, they are written on the same line as the variable name and
parentheses.
fix the lists indentation
`flyspell-correct-word-generic` and `flyspell-correct-previous-word-generic` are
deprecated and replaced by `flyspell-correct-at-point` and
`flyspell-correct-wrapper` respectively.
`flyspell-correct-wrapper` has a so-called 'rapid' mode, where you can correct
multiple words in a single run.
Syntax-checking and auto-complete layers should more
directly communicate that their function depends on
the installation of individual language layers to avoid
misunderstandings with new users who only install
syntax-checking or auto-complete and install the packages
manually.
This reverts commit 29c78ce841 and all other fixes
that have been made afterwards.
The motivation is that use-package is seen by many as a replacement for
`require`. Is use-package always defer the loading of packages then is breaks
this use case, this does not respect POLA so even if it was making Spacemacs
loading faster (up to 3s faster on some startup on my machine) we just cannot
use it, it would be irresponsible. Spacemacs should be easy to use, loading
performance will come with time but it is not a priority.
Added:
- Information about incompatibility of vim-empty-lines and spell-checking
inside org-mode.
- Features section to Description section (to comply with standard).
- Section how to enable multi-dictionary for hunspell.
spacemacs/add-flycheck-hook was not really hooking anything, change the name
to better reflect what it does.
Also changed the push for a add-to-list to avoid duplicates.
Flycheck recently gained a feature to explain the error at point (bound
under `C-c ! e` by default). This commit adds a corresponding leader
binding to the flycheck layer.
