C-o and C-i are standard vim keybindings to jump back/forward between previous
locations. It is annoying and unnecessary that evilified buffers break that
flow, therefore these keybindings should be added to the
`evil-evilified-state-map` so that they are available automatically in all
evilified keymaps/modes. I assume that by just adding them to the map, all
required remappings will automatically be taken car of by the
`evilified-state-evilify-map` macro (anyway, it seems to work fine).
Move closing parens on all dotspacemacs/user-* functions to a new line so the
function documentation and closing paren are not part of the config diff when a
user runs `SPC f e D`. This should make it faster to check config changes versus
the template.
lsp-use-upstream-bindings is t so by default spacemacs will use lsp-mode binding
scheme. We should consider to phase our the current manual binding scheme for
lsp-mode in future
The config for git-gutter currently sets custom fringe bitmaps which
are optimized for half-width fringes.
I think that's an arbitrary choice. There's no spacemacs option which
enables half-width fringes and as far as I can tell, we don't optimize
for half-width fringes anywhere else. So we should optimize the
package defaults for the spacemacs default of full-size fringes.
If users set half-width fringes manually, they can customize the
bitmaps manually. Even if they don't, the bitmaps are still visible,
they just don't look as nice.
* [languagetool] fix for non standard language code
In the language tool layer, the `languagetool-get-language` function is used to
deduce the correct language code for languagetool from the variable
`ispell-local-dictionary`, `ispell-dictionary`, or from the list
`ispell-dicts-name2locale-equivs-alist` by replacing dash by underscore. However
many lanagetool codes are not formatted consistently with what can be found in
ispell, check `languagetool --list <file>` for the exact list.
Therefore I created this list of convertion between ispell codes and lanagetool
codes.
* [languagetool] Reorder language code by usage
* [languagetool] translate non-obvious language code
special-case handle the translation when a simple conversion from underscore to
dash does not work
Co-authored-by: emiltoacs <mil@evo.nomail>
This reverts commit f2755533de.
This adds fix for julia layer breaking yasnippet setup.
Commit f2755533de fixed a specific bug in julia
layer but it loads yasnippet and friends on start up which adds 1 sec to my
startup time even though I don't use julia.
Julia layer loads lsp-julia early on startup, which loads lsp who then loads
yasnippet behind the scene unknown to spacemacs and use-package. That's why our
nice and ordered setup for yasnippet and yasnippet-snippets failed as discussed
in https://github.com/syl20bnr/spacemacs/pull/15171. We now tell use-package to
defer its load.
Follow mode in the pdf-occur buffer is very handy, and deserves specific
Spacemacs keybinding (mainly for discoverability/documentation, as its name
`next-error-follow-minor-mode`, putting it mildly, is not very intuitive)
The fix introduced in 23367d08f8 NOPs
evil-redirect-digit-argument. As a result, pressing 0 while in iedit movement
state does not jump to the beginning of the match or beginning of line.
This change redefines the functions currently needed by evil-iedit-state while
keeping the expected functionality
iedit does not work already for quite some time. A fix (see
https://github.com/syl20bnr/evil-iedit-state/pull/37) has been proposed, but it
does not get merged (even after multiple reminders). Therefore, I propose to add
this temporary quick fix, that can/should be removed after that PR gets merged.
Seems that we have a lot of places where
evilified-state-evilify has been used
instead of evilified-state-evilify-map.
This causes issues with shadowing of
evilified maps as this is only done by
the later of those two.
Fixes#15150
The auto-completion layer seems not to have been designed/configured correctly.
So that, e.g., when using the julia layer, the `auto-completion/init-yasnippet`
function is called after the `yasnippet-snippets` package has been loaded.
Despite the ``yasnippet-snippets` package containing an `eval-after-load
'yasnippet`, the form within that block is, for some reason, evaluated already
before `auto-completion/init-yasnippet` has been called.
Anyway, what currently happens is that first `(yasnippet-snippets-initialize)`
is evaluated, adding `yasnippet-snippets-dir` to the `yas-snippet-dirs` list.
Then ``auto-completion/init-yasnippet` is called which contains the line `(setq
yas-snippet-dirs nil)`, setting the list to nil again.
As there is quite some logic involved (e.g. the order of evaluation is correct
when the julia layer is not being used), this commit fixes the reported issue by
simply calling `(yasnippet-snippets-initialize)` from
`auto-completion/init-yasnippet` after the yas-snippet-dirs list has been
resetted to nil.
Any cleaner solution is welcome, but I would say this is a 'harmless' very
pragmatic quick fix/solution.
* [git] Fix: Evil-collection @-dispatch keybindings for magit forge.
Load new location for forge '@' dispatch keybindings.
'Evil-collection' has moved keymaps for magit forge from an
'with-eval-after-load' block to newfile 'evil-collection-forge.el' in commit
33461aa545.
As mentioned in the commit, these changes were due to a upstream change in the
'forge' package. Source: https://github.com/emacs-evil/evil-collection/issues/543
* [git] Docs: update README to reflect changes in Forge keybinds.
See https://magit.vc/manual/forge.html#Introduction for more information.
* lsp: Bind =~SPC m g T~ to lsp-treemacs-type-hierarchy
This allows to show the type hierarchy for the type at point.
* lsp: Goto call and type hierarchy are provided by lsp-treemacs
Maxi Wolff
Julio Rincon
SpacemacsBot
Lucius Hu
Daniel Nicolai
Lin Sun
Evan Klitzke
Liu Zhijun
SpacemacsBot
Elliott Shugerman
Harvey Chapman
Thanh Vuong
shdennlin
Tim Ruffing
emiltoacs
emiltoacs
Lucius Hu
Chris Jenkins
Rodrigo Kassick
Kijima Daigo
deb0ch
Hans
Wieland Hoffmann