forked from syl20bnr/spacemacs
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jg-made personalised spacemacs #1
Open
jg-made
wants to merge
452
commits into
develop
Choose a base branch
from
jg-made
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jg-made
force-pushed
the
jg-made
branch
2 times, most recently
from
December 5, 2019 10:58
b01e889
to
374d02a
Compare
otherwise it throws warnings when layers introduced imperatively, e.g.: dotspacemacs-configuration-layers `( ,(when (eq system-type 'darwin) 'osx) ,(when (eq system-type 'gnu/linux) 'exwm))
Change some leader keys for Julia, R, Inferior. Remove noweb bindings for Julia and R since it no longer works. Add LSP backend support for R.
Before ess layer was always using non lsp completions, this I have corrected by conditionally set company-lsp or the standard ess backends.
Per discussion in syl20bnr#13164, we have a standard, consistent technique for doing this across any layer. Provided that `global-company-mode` is not set, this works as expected to disable company without requiring custom variables.
Previously, this would try to add the lsp jump handler to the mode's jump handler list every time lsp started managing a buffer of that mode. Now, we only use the lsp jump handler for buffers managed by lsp.
The cl package has been deprecated. It had aliases for cl- prefixed commands without the cl- prefix. Ex: letf or letf* instead of cl-letf or cl-letf* On the `spacemacs-base` distribution, with the `ivy` layer. When one tries to search with `SPC /` (which calls `spacemacs/counsel-search`) Then this error message is shown: >spacemacs/counsel-search: Symbol’s function definition is void: letf* It doesn't happen with the `helm` layer, because it's search commands already has the `cl-` prefix. There are also three instances of: `letf` in the `spacemacs-editing-visual` layers functions: - `spacemacs/toggle-centered-buffer` (`SPC w c c`) - `spacemacs/toggle-distraction-free` (`SPC w c C`) - `spacemacs/centered-buffer-transient-state` (`SPC w c .`) Without the `cl-` prefix they show the error message: >Symbol’s function definition is void: letf
even though we have a check if doom is actually set in dotspacemacs-mode-line-theme in doom mode line init function. doom-modeline still adds a bunch functions to hook `after-change-functions regardless of the value of mode line theme name. Hence we need to put a toggle on the declaration
Added following themes: * doom-acario-dark * doom-acario-light * doom-horizon * doom-laserwave * doom-manegarm * doom-material * doom-oceanic-next
There's no keybinding for markdown-insert-kbd alongside all the other markdown-insert-* keybindings, this patch adds one using the same convention (specifically xk).
`lsp-mode` supports two LSP server backend for Rust language, i.e. `rls` and `rust-analyzer`. `rust-analyzer` is experimental and lacks certain functionalities such as `DAP` support. `lsp-mode` provides a function `lsp-rust-switch-server` that changes the priority of LSP server backend for *new* LSP session. This commit adds a key binding `SPC m s s` to `lsp-rust-switch-server`.
When entering insert mode, don't start editing in the middle of the prompt text. That is, given: ~/foo/bar> some command ^ ^ ^ A B C Cursor A will jump to position C but cursor B won't. Edit by duianto This also stops the cursor from jumping to the end of the last line, when entering insert state, from all but the last line in a multi line. Example: ~/foo/bar>(+ 1{cursor in normal state on the 1} 2) Entering insert state: i Before: ~/foo/bar>(+ 1 2){cursor in insert state after the close parenthesis} After: ~/foo/bar>(+ {cursor in insert state before the 1}1 2)
Added some missing thanks. Added some line breaks to keep the lines under 80 chars.
This binding toggles the electric terminator setting of Proof General. Also describe the new binding in the README and add a note to the change log.
This commit contains the following original ones: [dump] don't assume spacemacs start directory when dumping [dump] dump to a temporary file and atomically rename it [dump] cleanup after dumping
…g-mode Also removed `ein:company-backend` during initialization since it does not exist anymore.
The warning: nlinum layer is deprecated for Emacs 26.1 and above wasn't shown until SPC h SPC was pressed. Because the variable: configuration-layer--used-layers wasn't populated before the warning check occurred in nlinum/packages.el. The solution (suggested by syl20bnr) was to move the check to a new file: nlinum/config.el.
Also fixed the groovy/funcs.el header which said: Java
Enhances `sqlfmt` support in SQL layer. `sqlfmt` was only being applied against the whole buffer, and did not allow invocation against a specific region in the buffer. `sqlfmt` customize options were not included under the `sql` group. It was not possible to control if `sqlfmt` reused an existing error buffer or generated new ones. - Added `sqlfmt-region` interactive command and binding under `sql-mode` keymap - `sqlfmt-buffer` calls into `sqlfmt-region` with `(point-min)` and `(point-max`) - Added `sqlfmt` customize group as child to `sql` customize group - Added `sqlfmt-reuse-error-buffer` option - Updated `sql` layer documentation to reflect changes
Add installation instruction for `sqlfmt` executable Adapt documentation to be more like the other layers Replace wrong default sqlfmt parameter -u with --use-spaces Make error buffers be reused by default to reduce memory consumption Change prefix for repl keybindings to be conform with the other layers Remove obsolete progn statement
There is a popular question about openning file in exact window. There is an ace mode for that, but it is not so clear how to use it for new users. That commmit add information how to use ace mode and how tweak it based on information from Alexander-Miller/treemacs#266
Following the advice from duianto syl20bnr#13100 we are setting completion-styles for helm-M-x to include the emacs version specific fuzzy strategy as last resort. Before no fuzzy matching occured within command searches.
To optimise performance of lsp mode in emacs 27 and above I have introduced a new dotfile variable to define the size of data read from external processes. The default I have set to the recommended setting from lsp-mode. In addition I have introduced a new layer variable for auto-complete-layer to define the minimum prefix length. I have also added instructions to auto-complete's readme how to set these variables to the recommended settings for lsp-mode. Changes inspired from syl20bnr#13507
Install ubuntu(18.04) libvterm-dev will cause compilation error, update latest doc from emacs-libvterm, it shall download latest libvterm automatically.
racket-xp-mode is an optional minor mode that enhances the racket-mode to explain and explore Racket code. The racket-xp-mode is started with a mode-hook on racket-mode. Deprecated racket-mode functions are replaced with their racket-xp-mode versions. The remaining racket-xp-mode functions are added to keybindings as per Spacemacs conventions. Also add the racket-mode directory to .gitignore.
If not done plantuml-mode will try to work with the online server and fail during parsing of its response. Reported in syl20bnr#13574
The variable: layouts-enable-local-variables and function: spacemacs/make-variable-layout-local are defined in the layer: spacemacs-layouts But the spacemacs-layouts layer isn't loaded in the distribution: spacemacs-base
The previous way of adding dap to a layer did add the mode unconditionally to `spacemacs--dap-supported-modes` causing dap bindings to be added also when no lsp backend was used.
…ge-server Removed suggestion to manually install Python packages that are already dependencies of python-language-server [1]. [1] https://github.com/palantir/python-language-server/blob/6a7eae7600a17b4f076263016639ff2a430b72e3/setup.py#L50-L58
A BEGIN_SRC block in the documents had no language specified which would break CI. I have also changed the eldoc setup to run each time the mode is entered instead of only in the initially loaded buffer.
The Neotree layers.el header said: Treemacs Capitalized Treemacs Appended: for Spacemacs (most of the layer files first line seems to end with that)
From the author of mu4e, org-mu4e.el is not supported anymore. Load the supported org functionality from mu4e-org.el instead. mu4e author -- "org-mu4e.el has been obsoleted in mu4e 1.4.x... the supported parts are in mu4e-org.el now. And there's currently no real expectation you can load those separately (it might work)." I believe by separately means loading mu4e-org w/o having loaded mu4e.
Flycheck-golangci was not properly conigured which resulted in not replacing disabled standard linters like go-test. In addition there seems to be an issue in the current golangci build causing the linter to fail. In this case spacemacs now shows at least basic errors from go-build. When they are fixed the linter should be able to work normally again.
…re found Before the decision which linter to run before golangci-lint has been taken by the layer. However this can also directly be done by the checkers. Also golangci-lint did run even when the previous checker still reported errors. With this it is only called if the previous checker is satisfied. All thanks goes to Tommi Komulainen.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nobody else wants this stuff but it's fun to see it in my own PR