* create visual selection from transient paste
Improve "Pasting Transient State" by adding a shortcut C-v to generate a visual selection from pasted test.
* Remove unnecessary lambda expression
Commit 54f12b66f correctly moved code-cells setup to use-package's :init to
ensure that python-mode had a hook for code-cells-mode -- otherwise, code-cells
would never be loaded automatically with python major mode.
A side-effect of this change was that now there was a minor mode keymap for
`code-cells-mode` , which may not have been loaded unless emacs has already
opened a python file.
When calling `describe-key` , the function `help--binding-locus` would iterate
over `minor-mode-map-alist` and, when it reached the entry for code-cells-mode,
a call to `(symbol-value 'code-cells-mode)` would fail with a `void-variable`
error. Despite `code-cells-mode` being an auto-loadeable symbol, `symbol-balue` would not trigger the autoload.
The solution (as pointed by @sunlin7) was to call `add-hook` on `:init` and
`spacemacs/set-leader-keys-for-minor-mode` on `:config`
Currently, due to evil entering visual state, the selection behavior in
pdf-tools is different from and more cumbersome than in vanilla Emacs (see
https://github.com/emacs-evil/evil/issues/1671).
This commit prevents evil from entering evil-state in pdf-mode and moves the
(only) visual-state yank binding to the evilified-map.
It doesn't look pretty, but it is working much better than before.
* 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
* [docker] Followup for #15414: Fix bindings not being added, add docs.
* [docker] Wrap `:config` block in a `progn`, as per CONVENTIONS.org.
* [docker] Fix key binding in documentation.
Co-authored-by: Tommi Komulainen <tkomulai+github@gmail.com>
Co-authored-by: Tommi Komulainen <tkomulai+github@gmail.com>
lsp-julia-default-envornment is set by default to ~/.julia/environments/v1.0 .
To make the lsp server show completions for installed packages, the environment
location must be the same as that of the installed julia version enviornment.
Documentation was added to notify users to set the emacs variable to their
enviornment location.
- Removed unnecessary package `persistent-soft`. This is never actually used by
Spacemacs. And it's automatically installed as a dependancy package of
unicode-fonts anyway.
- Properly use `use-package` to initiate `ligature` package.
- Improved README.org and config.el.
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)
- Updated layer README.org to include prerequisites
- Removed unnecessary layer config variables which are mere re-naming
of customization variables from `parinfer-rust-mode`.
- Removed the image.
1. move posframe package into spacemacs-visual layer for package sharing
2. add `pre-int-posframe` and `post-init-posframe` for further configurations
Rebase to the latest code and remove posframe from translate layer
[translate] allow user to customize renders
This reverts commit 91af298090.
it breaks (kill-whole-line) `kill-whole-line` (C-S <backspace>)
the SO link mentioned in it got 0 point.
and hack like this can be put it to user's own config.
When `dotspacemacs-enable-paste-transient-state` is on, there exists a minor
annoyance that deleted whitespaces appear in the kill ring. This requires an
extra C-j/C-k to bypass the noise.
This commit uses a advice function to `kill-new` to prevent text with only
whitespaces from entering kill ring.
Credit: https://stackoverflow.com/questions/12102554/emacs-skip-whitespace-kills
Co-authored-by: Lucius Hu <1222865+lebensterben@users.noreply.github.com>
Co-authored-by: Lucius Hu <lebensterben@users.noreply.github.com>
- 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.
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.
Ralph Landon
rommeswi
Joshua Wood
Lin Sun
Daniel Nicolai
Irsyad Asyhari Lubis
Rodrigo Kassick
Maxi Wolff
Codruț Constantin Gușoi
Richard Kim
Jen-Chieh Shen
Atemu
Alfonso Montero
Cédric M. Campos
Lucius Hu
Elliott Shugerman
iliekprogrammar
Lucius Hu
SpacemacsBot
Diego Caples
SpacemacsBot
Ray Wang
Gunnar Bastkowski
Michael Bauer
Bai, Yang
Thanh
Skylar Hill
Ben
Nathanael Schweers
Tim Ruffing
Aaron L. Zeng
Lin Sun
Alfonso Fernando Álvarez