Don't start the lsp server until after mspyls is optionally required
Otherwise, lsp will attempt to use pyls when the user wanted to use mspyls
This commit is contained in:
parent
556433f95c
commit
054856be3d
|
@ -2353,6 +2353,7 @@ Other:
|
|||
- Various fixes for =lsp-python-ms= setup (thanks to Trapez Breen)
|
||||
- Added lazy loading of =lsp-python-ms= (thanks to Ying Qu)
|
||||
- Make pylookup makefile use correct shell (thanks to Koray Al)
|
||||
- Fix lazy loading of =lsp-python-ms= (thanks to lsp-ableton)
|
||||
**** Racket
|
||||
- Restore smart closing paren behavior in racket-mode (thanks to Don March)
|
||||
- Updated racket logo (thanks to Vityou)
|
||||
|
|
|
@ -62,9 +62,9 @@
|
|||
"Setup lsp backend."
|
||||
(if (configuration-layer/layer-used-p 'lsp)
|
||||
(progn
|
||||
(lsp)
|
||||
(when (eq python-lsp-server 'mspyls)
|
||||
(require 'lsp-python-ms)))
|
||||
(require 'lsp-python-ms))
|
||||
(lsp))
|
||||
(message "`lsp' layer is not installed, please add `lsp' layer to your dotfile."))
|
||||
(if (configuration-layer/layer-used-p 'dap)
|
||||
(progn
|
||||
|
|
Loading…
Reference in New Issue