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.
The default logo is rather big. Users might prefer to use the screen size for
other information (while still showing a banner).
This commit adds a configuration variable `dotspacemacs-startup-banner-scale`
to the dotfile
The script used to identify and update the change is added into the GitHub
workflows script directory. A workflow action can be created to trigger the
script to update the headers on the first of every new year. Possibly a task for
a consequent PR.
Previously, `SPC t n n` (spacemacs/toggle-line-numbers) did not respect
dotspacemacs-line-numbers despite it telling otherwise, when it's binded to a
property list.
with this curent (package :location local) can be replaced with (package
:location (recipe :fetcher local)) then quelpa will install local pacakge. We
have the benefit of bytecompile and autoload
[packages] use new fetcher for local
