- Added a new layer variable `nav-flash-exclude-modes` which tells
`nav-flash/blink-cursor-maybe` not to trigger when the major mode matches one of
its elements.
- Expanded the documentation.
- Tidying up.
This commit contains adjustment to layer documentatin.
Specifically it added more information on key bindings in
`flycheck-error-list-mode` and adjusted the order of a few sections.
- Removed redundant keybinding for `RET`, which is already defined in
`flycheck`.
- Added two keybindings to move the focus to next/previous line without also
viewing the corresponding error in the other window.
Due to an error of argument order, `syntax-checking--buffer-config` was not
declared correctly and the setting is not respected by `popwin`.
This commit fixed that.
Before this commit, users are not informed of the option to use margins, in
addition to fringes, to display flycheck indicators. This commit provides
clearer information on customizing this. Specifically:
- Added instruction on how to change the location of flycheck indicator.
- Added a new layer variable `syntax-checking-indication-symbol` which allows
customization for symbol used for flycheck indication.
- Deprecated the layer variable `syntax-checking-use-original-bitmaps` in favour
of `syntax-checking-indication-symbol`, because the latter allows a finer
control of both fringe bitmap and margin string.
When toggling off flycheck's error list window, it calls `quit-window` which
might also change the focus to another window.
Wrapping this form `save-selected-window` ensures the focus always returns to
where toggling command is first invoked.
`term-cursor` was added to provide configurable cursor shape and colour when
Emacs is running in a terminal. Originally, it would not be enabled when the
user is using `evil` editing style, as `evil-terminal-cursor-changer` seems to
be a better alternative.
As explained in commit #d48bc8d9 `evil-terminal-cursor-changer` has buggy
behaviours and was removed. This commit therefore enables `term-cursor` for all
editing styles in terminal Emacs.
This package was added years ago but promptly removed due too buggy behaviours
with certain terminal and OS combination.
This commit entirely removed this package since there has been no update from
the upstream for years.
There is an unreported bug that when startup list is set to shown `recents-by-project`,
Emacs reports that `projectile-mode` is an unknown symbol.
This commit fixed this bug by checking the existence of `projectile-mode`, which is
automatically loaded during startup.
mu version 1.8.2 renamed mu-meta to mu-config. As the variable mu4e-mu-version
is defined in said file the easiest fix seems to be to simply attempt to load
the new one, and only if that fails to load the old version.
Maybe this can be reworked or better yet removed in the future.
magit v3.2.0 now defines `magit-git-executable` as a
function (actually a defsubst), and two separate variables,
`magit-git-executable` and `magit-remote-git-executable`. On darwin,
magit already sets `magit-git-executable` to the result of
`(executable-find "git")`, so having this is now redundant in
Spacemacs.
This is an extension of #15462. I noticed that the fix did not apply
to magit-diff buffers, which still had the issue of `s' not being
available to stage diff hunks. `magit-diff-mode' is the parent mode
of all magit modes, in which evil-surround is not useful, so disabling
there makes the most sense.
1. Delete vim-empty-lines layer and merge its code into spacemacs-evil
2. Remove unused function from spacemacs-evil/funcs.el
3. Add variable dotspacemacs-evil-show-empty-line-indicators to toggle vim-empty-lines-mode
4. Update related documents
5. Compatibilities
This variable caused Spacemacs to set all helm sources
to use fuzzy matching independently of whether this
was supported by the source.
This handling was very dangerous as using fuzzy for an
incompatible source can have all kind of side effects
causing unique bugs which will never be fixed by the
source package authors.
Therefore I have changed the implementation to
activate fuzzy matching via helm variables instead,
which should make sure we only activate this for
compatible sources.
If sources are found which do not longer do
fuzzy matching, the individual source should be
improved to support this feature and declare it's
compatibility towards helm.
We cannot fix helm in Spacemacs, instead the respective
package must be patched. Everything else is a maintenance
nightmare!
Fixes#15124
This work around is taken from dalanicolai's comment on #15505.
It tries to circumvent a name clash between the emacs package
"restart-emacs" and emacs 29 which introduced a function called
"restart-emacs".
The workaround is to load the package after the emacs file
module has been loaded.
Change variable declarations to standard config variables.
Change default size to relative values to be less independent
on specific screen sizes.
Improve general documentation of config choices.
A final 'force push' to PR #15574 implemented functionality to make the banner
size depend on the actual 'startup list' instead of the configured maximum
startup list size. However, that 'new' functionality uses
`spacemacs-buffer//do-insert-startupify-lists` which activates `recentf-mode`,
and unfortunately, activating `recentf-mode` this early in the startup process
somehow breaks recentf functionality, see comments at
a485b5a84b.
This commit 'reverts' the functionality by making the banner size depend on the
configured maximum startup list size.