* compleseus: disable ido-mode when vertico and selectrum are used
ido would inject inself instead of the regular `find-file' but if these are
activated, we actually want the regular `find-file'.
* core: provide minibuffer evilification predicate
Many different layers need to decide whether to evilify their minibuffer maps.
Provide a single function that puts the logic in one place.
* compleseus: only evilify minibuffer binds when desired
For `helm` users, we set `xref-show-xrefs-function` according to Emacs version.
This is a two-fold unnecessity:
- We now only support Emacs version > 27, so `hellm-xref-show-xrefs` should not
be used anyway.
- `hem-xref` already set this variable according to Emacs version. See
[here][ref].
This commit removes this.
ref: ea0e4ed8a9/helm-xref.el (L192-L197)
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
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.
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
- update vertico-repeat
- annotation for projectile
- tweak xref
- new buffer source of modified ones
- vertico settings
- use consult-org-heading
- tweak orderless
- tweak consult-line to start from top to bottom
- tweak marginalia
- tweak orderless for company and lsp
- fix persp mixing up buffer-list order
* Fix function quote warning
Change `'` to `#'`, resolves#15443.
* Fix quoting in `helm-spacemacs-help.el`, add docstrings, fix action
These changes hopefully fix#15443
- Add docstrings to the lambdas
- Change selected action for `<S-return>` to the sixth action, to install the
layer. This change makes the action conform to the removed comment.
> `;; Add layer`
* squash! Fix function quote warning, fix helm action
- Resolve#15443
- Add docstrings to lambdas
- Fix index of helm action for layer install (the actions are zero-indexed)
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
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.
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.
* [compleseus] layout select current project first
* [compleseus] bind embark-export to C-c C-o
same as ivy-occur
* [compleseus] add vertico-{quick, directory}
* [compleseus] set up vertico-repeat
Currently most or all auto-completion, using completion-at-point (i.e. the TAB
key), is 'hijacked' by company-capf in emacs-lisp-mode, while in text mode there
is no auto-completion by default at all.
This commit adds auto-completion for text-mode and slightly improves the
situation for emacs-lisp mode.
* Add commands to compleseus+fasd layer (locate,yasnippet,search-from)
* Add metadata classifier (for embark) to fasd-layer
Embark uses metadata of the target under point to determine actions. If the
target lacks a metadata classifier then the [embark
documentation](https://github.com/oantolin/embark#acting-on-targets) recommends
to [add them using the marginalia package](https://github.com/minad/marginalia#adding-custom-annotators-or-classifiers).
This PR adds the file classifier to results for fasd searches.
Lin Sun
Steven Lin
Irsyad Asyhari Lubis
Atemu
Lucius Hu
thanhvg
Maxi Wolff
Arif Er
Sebastian Hahn
Daniel Nicolai
Bryce
Dan Kessler
Alfonso Montero
Andreas Sahlbach
Lucius Hu
ismama
SpacemacsBot
Robert O'Connor