- 22 Apr, 2021 1 commit
-
-
Sylvain Benner authored
-
- 21 Apr, 2021 7 commits
-
-
Kjartan Óli Ágústsson authored
Added header. Removed cl-generic dependency which is not needed for current minimum version (or later) of Emacs.
-
Kjartan Óli Ágústsson authored
`first` and `list-length` are aliases for `car` and `cl-list-length` respectively. Using these aliases causes emacs to error with a `symbol's function definition is void` error, but using their real names causes no error. Replaced them with `car` and `length`.
-
Kjartan Óli Ágústsson authored
Co-authored-by:
Lucius Hu <1222865+lebensterben@users.noreply.github.com>
-
Aaron Zeng authored
-
Aaron Zeng authored
-
wildwestrom authored
You can now export org files as asciidoc documents.
-
ralph-cheng authored
-
- 19 Apr, 2021 11 commits
-
-
emacspace authored
-
Maximilian Wolff authored
-
Diego Berrocal authored
* Add Emacs Window Manager (EXWM) Layer The time has come of SpacemacsOS * set window manager name to EXWM * update copyright notice * start server when EXWM is active When using EXWM, Emacs should be ready to receive clients but the final choice should be the user's in their shell configuration. * respect Spacemacs naming conventions and layer organization * leave keyboard remapping to users * add EXWM states for Evil * add support for helm-exwm when helm is in use * use both exwm-randr and exwm-systemtray * set up workspaces to match displays by default * use ido-config instead of the deprecated workaround When using helm-exwm, its sources distinguish title and class automatically. It is only necessary to keep the buffer name updated when the window title changes. When using ido, rename differently for different applications. * add bindings for common X keys * use standard prefix commands where available Spacemacs already has prefix commands for controlling windows. These are directly available in exwm-state as well as in exwm-insert-state through leader * remove most keybindings as they are available directly in exwm-state * enable exwm directly in the layer configuration It is safe to enable it here as an existing window manager will simply fail with a warning. * add user-configurable variables for RandR and workspaces By default, create as many workspaces as there are displays and assign them in RandR order. * fix naming convention for variables * use helm for launching applications when possible * fix conditional helm-exwm leader keys * remove redundant function EXWM provides the equivalent * conform to naming convention for Spacemacs * separate prefix commands into those for major mode and global * remove all default bindings * improve readability * clean up bindings * remove obsolete comments Co-authored-by:
M. Domenzain <luis.domenzain@parrot.com>
-
Thanh Vuong authored
Ported from Doom
-
Maximilian Wolff authored
Private variables must use "--" after the prefix.
-
Thanh Vuong authored
bind it to `spc r w`
-
Thanh Vuong authored
bind it to `SPC x x`, not sure it's the right place but it's easy to invoke
-
Daniel Nicolai authored
Racket describe mode comes with its own keybinding (i.e. `q` for quit). Additionally it contains links, so this PR binds `o` to `link-hint-open-link` (`ace-link` does not support this mode)
-
Daniel Nicolai authored
The layer got broken due to some minor changes in the eaf package by the eaf developers. This commit fixes the layer to a working state.
-
Lucius Hu authored
* core-customization: improved SAFE variable handling - SAFE can either be a function or t. - When it's t, use a default validation function `(lambda (val) (validate-value val TYPE t))` - When it's a function, use the supplied function. * Fixed bugs in go and groovy layer In almost any cases, it's better to supply `t` instead of a function, to `SAFE` argument of `spacemacs|defc`. For example, ```elisp (spacemacs|defc go-use-gocheck-for-testing nil "If using gocheck for testing when running the tests -check.f will be used instead of -run to specify the test that will be ran. Gocheck is mandatory for testing suites." 'boolean nil #'booleanp) ``` If its value is nil, it evaluate to `nil`, which means that `nil` is not a safe value for `go-use-gocheck-for-testing` local variable. But clearly it is. * core-customization: improved SAFE variable handling - Added a function `spacemacs-customization//get-variable-validator`. This function is designed to be used with `safe-local-variable` property of spacemacs custom variables. See details in the docstring. ```elisp (put 'FOO 'safe-local-variable (apply-partially 'spacemacs-customization//get-variable-validator 'FOO)) ``` - This is better than a lambda since `apply-partially` returns a compiled function. (Though the performace gain may be tiny.) - This is better than simply calling `validate-value`, because it returns nil when value is nil. But sometimes nil is a valid value. Co-authored-by:
Lucius Hu <lebensterben@users.noreply.github.com>
-
Luis Ch authored
-
- 18 Apr, 2021 1 commit
-
-
Sylvain Benner authored
With this fix it is now possible to select different backends in different project using the directory variables mechanism of Emacs (the file .dir-local.el)
-
- 17 Apr, 2021 9 commits
-
-
Maximilian Wolff authored
and fix wrong declaration of go-mode hooks
-
Maximilian Wolff authored
-
Lucius Hu authored
- Labelled `go-backend` and `go-format-on-save` as safe local variable. - Added local variable hooks of go mode: - `spacemacs//go-setup-backend` - `spacemacs//go-setup-eldoc` - `spacemacs//go-setup-format` See: https://github.com/syl20bnr/spacemacs/issues/14653
-
Maximilian Wolff authored
-
Maximilian Wolff authored
And extend spacemacs|defc to allow setting a :safe directive.
-
Lucius Hu authored
- Labelled `groovy-backend` as safe local variable. - Added local variable hooks of groovy mode: - `spacemacs//groovy-setup-backend` - `spacemacs//groovy-setup-company` See: https://github.com/syl20bnr/spacemacs/issues/14653
-
Maximilian Wolff authored
Eww was wrongly classified as web-service. It can now be found under tools hence the global binding was changed from `SPC a w e` to `SPC a t e`. Also I have removed parts of the documentation still refering to this layer not being part of Spacemacs.
-
emacspace authored
-
JAremko authored
-
- 15 Apr, 2021 11 commits
-
-
Maximilian Wolff authored
-
Maximilian Wolff authored
This commit combines all changes from the above mentioned fork from the original author. All praise goes to dalanicolai.
-
coljamkop authored
A spacemacs layer that adds: - Improved spacemacs functionality to eww-mode - Evil keybindings to eww-mode (including eww-buffers/bookmarks/history-mode) - Improved eww buffer management with key bindings
-
Maximilian Wolff authored
-
Lucius Hu authored
-
Maximilian Wolff authored
-
emacspace authored
* documentation formatting: Thu Apr 15 19:58:45 UTC 2021 * Built-in files auto-update: Thu Apr 15 19:57:01 UTC 2021
-
pataquets authored
-
duianto authored
Fixes: vim layer key binding of "J" in dired mode #14614 https://github.com/syl20bnr/spacemacs/issues/14614 problem The evil collection binds "J" to `dired-go-to-file` It overrides the Spacemacs `helm` and `ivy` equivalent commands. `spacemacs/helm-find-files' has fuzzy matching and other features `spacemacs/counsel-find-file' has more `M-o' actions And the `ivy` layer uses the `spacemacs/helm-find-files` command. solution Move the Spacemacs definitions of "J", after the evil collection dired keys have been setup from: `spacemacs-bootstrap/packages.el` to: `spacemacs-evil/init-evil-collection` And use `spacemacs/counsel-find-file` in the `ivy` layer.
-
duianto authored
problem In the `spacemacs-base` distribution. When the `git-enable-magit-todos-plugin` layer variable is enabled. Then the following message appears on startup: >An error occurred while pre-configuring magit-todos in layer git (error: (void-variable spacemacs-evil-collection-allowed-list)) cause The `spacemacs-evil-collection-allowed-list` variable is assigned in the `git` layer. But it's defined in the `spacemacs-evil` layer. The `spacemacs-evil` layer isn't used by default in the `spacemacs-base` distribution. solution Check that the `spacemacs-evil` layer is used before adding to the variable.
-
Daniel Nicolai authored
For introspection purposes it can be nice to have this functionality. Also this function can be used to discover which ex-commands are available.
-