Using the prefix argument does not work nicely with evil since it is
already used to paste several times. Instead we use the universal
argument. To make it work with the evil functions we have to do some
trick to hide the universal argument temporarily (see around advice).
This is a nice feature taken from Prelude. This commit advises yank and
yank-pop and evil-paste-after to indent after pasting, unless a prefix
arugment is specified or the major mode is one of
spacemacs-indent-sensitive-modes.
Conflicts:
contrib/better-defaults/README.md
It is not needed in this case because a post-init does not mark
the package as used (so if there is not init function for company
it won't be installed and the post-init function won't be evaluated)
It is reported in this issue: https://github.com/company-mode/company-mode/issues/180
that company has distorted completion popup with fci-mode turned on.
Company maintainer proposed a fix for this issue that is added in this
commit.
Having fci-mode to visually indicate the limit of commit message region
is nice. With it, we know exactly our text does not cross the limit (i.e
72 columns). Sometimes, text can cross the boundary if we add something
but use C-n or j to move to next line.
The current color is unreadable in dark theme since it uses
black. Change it to a color that readable in both dark and light theme.
Bonus: it looks nice in solarized light.
The `progn` in the eval-after-load was not quoted, so it was being
evaluated unconditionally. This led to the haskell-indentation guides
being unconditionally enabled.
Additionally, only enable the indentation guides when
haskell-indentation-mode is on.
Resolves#1136.
Currently using font-lock-preprocessor-face can make window number too
bright and distract. Use font-lock-comment-face to make it less
distracting while still visible since it's an inherent part of the
theme.
I found myself in <kbd>SPC : customize</kbd> without knowing how to switch out of it again when I was done, there was no menubar, and I couldn't turn it on either because the <kbd>SPC</kbd> keybindings or the Vim ones just didn't work at all.
Reading the documentation again I gave <kbd>fd</kbd> a try, and it brought the keybindings back, so I think it'd be helpful to mention that <kbd>fd</kbd> is also useful as an escape when the usual keybindings don't work.
Also wouldn't hurt if a message was displayed to use <kbd>fd</kbd> when trying to use <kbd>SPC</kbd> and it doesn't work.
