TakeV/spacemacs
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2024-10-22. You can view files and clone it, but cannot push or open issues or pull requests.
spacemacs/layers/+lang/fsharp/packages.el

89 lines
2.9 KiB
EmacsLisp
Raw Normal View History

Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
;;; packages.el --- F# Layer packages File for Spacemacs
;;
update copyright to 2020
2020-09-16 21:34:40 +00:00
;; Copyright (c) 2012-2020 Sylvain Benner & Contributors
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
;;
;; Author: Sylvain Benner <sylvain.benner@gmail.com>
;; URL: https://github.com/syl20bnr/spacemacs
;;
;; This file is not part of GNU Emacs.
;;
;;; License: GPLv3
Add fsharp layer
2015-03-10 23:11:29 +00:00
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
(defconst fsharp-packages
'(
company
counsel-gtags
flycheck
fsharp-mode
ggtags
helm-gtags
))
(defun fsharp/post-init-company ()
(spacemacs//fsharp-setup-company))
(defun fsharp/post-init-flycheck ()
(spacemacs/enable-flycheck 'fsharp-mode))
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
Add fsharp layer
2015-03-10 23:11:29 +00:00
(defun fsharp/init-fsharp-mode ()
(use-package fsharp-mode
Revert "Defer packages by default using use-package-always-defer" This reverts commit 29c78ce841ee5a99bb4077a2862afc96c8136107 and all other fixes that have been made afterwards. The motivation is that use-package is seen by many as a replacement for `require`. Is use-package always defer the loading of packages then is breaks this use case, this does not respect POLA so even if it was making Spacemacs loading faster (up to 3s faster on some startup on my machine) we just cannot use it, it would be irresponsible. Spacemacs should be easy to use, loading performance will come with time but it is not a priority.
2018-03-04 04:37:53 +00:00
:defer t
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
:init
Register all REPLs and make SPC m ' bindings
2016-01-26 16:31:15 +00:00
(progn
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
(unless (eq (spacemacs//fsharp-backend) 'lsp)
(require 'eglot-fsharp))
(setq eglot-fsharp-server-install-dir (expand-file-name
(locate-user-emacs-file (f-join ".cache" "eglot"))))
Register all REPLs and make SPC m ' bindings
2016-01-26 16:31:15 +00:00
(setq fsharp-doc-idle-delay .2)
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
(spacemacs/register-repl 'fsharp-mode 'fsharp-show-subshell "F#")
(add-hook 'fsharp-mode-hook #'spacemacs//fsharp-setup-backend))
Add fsharp layer
2015-03-10 23:11:29 +00:00
:config
(progn
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
(defun spacemacs/fsharp-load-buffer-file-focus ()
"Send the current buffer to REPL and switch to the REPL in
`insert state'."
(interactive)
(fsharp-load-buffer-file)
(switch-to-buffer-other-window inferior-fsharp-buffer-name)
Use evil in holy-mode Motivation While disabling Evil in holy-mode makes its implementation shorter and sounds elegant on the paper, in practice it puts a big burden on the configuration parts which need to know if Evil is enable or not. This is a bad separation of concerns and the bunch of fixes that we were forced to do in the past weeks shows this issue. Those fixes were about removing the knowledge of the activation of Evil by implementing new dispatching functions to be used by layers, this is cumbersome and makes Spacemacs layer configuration more subtle which is not good. There was additional bad consequences of the removal of Evil state like the impossibility to use Evil lisp state or iedit states, or we would have been forced to implement a temporary activation of Evil which is awkward. Instead I reintroduce Evil as the central piece of Spacemacs design thus Evil is now re-enabled in holy-mode. It provides the abstraction we need to isolate editing styles and be able to grow the Spacemacs configuration coverage sanely. Layers don't need to check whether the holy mode is active or not and they don't need to know if Evil is available (it is always available). We also don't need to write additional dispatching functions, this is the job of Evil, and I think it provides everything for this. Ideally configuration layer should be implemented with only Evil in mind and the holy-mode (and hybrid-mode) should magically make it work for Emacs style users, for instance we can freely use `evil-insert-state` anywhere in the code without any guard. Evil is now even more part of Spacemacs, we can really say that Spacemacs is Emacs+Evil which is now an indivisible pair. Spacemacs needed this stable API to continue on the right track. While these changes should be rather transparent to the user, I'm sorry for this experimental period, I failed to see all the implications of such a change, I was just excited about the possibility to make Evil optional. The reality is that Spacemacs has to embrace it and keep its strong position on being Emacs+Evil at the core. Implementation - insert, motion and normal states are forced to emacs state using an advice on `evil-insert-state`, `evil-motion-state` and `evil-normal-state` respectively. These functions can be used freely in the layer configuration. - A new general hook `spacemacs-editing-style-hook` allow to hook any code that need to be configured based on the editing style. Functions hooked to this hook takes the current style as parameter, this basically generalize the hook used to setup hjkl navigation bindings. - ESC has been removed from the emacs state map. - Revert unneeded changes - Revert "evil: enter insert-state only from normal-state" commit bdd702dfbe302206bbc989c7a0832daba087a781. - Revert "avoid being evil in deft with emacs editing style" commit f3a16f49ed27cc8cf05f23f93b006d6e04235381. Additional changes All editing style packages have been moved to a layer called `spacemacs-editing-styles` Notes I did not have time to attack hybrid mode, I should be able to do it later.
2016-03-13 23:41:18 +00:00
(evil-insert-state))
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
(defun spacemacs/fsharp-eval-phrase-focus ()
"Send the current phrase to REPL and switch to the REPL in
`insert state'."
(interactive)
(fsharp-eval-phrase)
(switch-to-buffer-other-window inferior-fsharp-buffer-name)
Use evil in holy-mode Motivation While disabling Evil in holy-mode makes its implementation shorter and sounds elegant on the paper, in practice it puts a big burden on the configuration parts which need to know if Evil is enable or not. This is a bad separation of concerns and the bunch of fixes that we were forced to do in the past weeks shows this issue. Those fixes were about removing the knowledge of the activation of Evil by implementing new dispatching functions to be used by layers, this is cumbersome and makes Spacemacs layer configuration more subtle which is not good. There was additional bad consequences of the removal of Evil state like the impossibility to use Evil lisp state or iedit states, or we would have been forced to implement a temporary activation of Evil which is awkward. Instead I reintroduce Evil as the central piece of Spacemacs design thus Evil is now re-enabled in holy-mode. It provides the abstraction we need to isolate editing styles and be able to grow the Spacemacs configuration coverage sanely. Layers don't need to check whether the holy mode is active or not and they don't need to know if Evil is available (it is always available). We also don't need to write additional dispatching functions, this is the job of Evil, and I think it provides everything for this. Ideally configuration layer should be implemented with only Evil in mind and the holy-mode (and hybrid-mode) should magically make it work for Emacs style users, for instance we can freely use `evil-insert-state` anywhere in the code without any guard. Evil is now even more part of Spacemacs, we can really say that Spacemacs is Emacs+Evil which is now an indivisible pair. Spacemacs needed this stable API to continue on the right track. While these changes should be rather transparent to the user, I'm sorry for this experimental period, I failed to see all the implications of such a change, I was just excited about the possibility to make Evil optional. The reality is that Spacemacs has to embrace it and keep its strong position on being Emacs+Evil at the core. Implementation - insert, motion and normal states are forced to emacs state using an advice on `evil-insert-state`, `evil-motion-state` and `evil-normal-state` respectively. These functions can be used freely in the layer configuration. - A new general hook `spacemacs-editing-style-hook` allow to hook any code that need to be configured based on the editing style. Functions hooked to this hook takes the current style as parameter, this basically generalize the hook used to setup hjkl navigation bindings. - ESC has been removed from the emacs state map. - Revert unneeded changes - Revert "evil: enter insert-state only from normal-state" commit bdd702dfbe302206bbc989c7a0832daba087a781. - Revert "avoid being evil in deft with emacs editing style" commit f3a16f49ed27cc8cf05f23f93b006d6e04235381. Additional changes All editing style packages have been moved to a layer called `spacemacs-editing-styles` Notes I did not have time to attack hybrid mode, I should be able to do it later.
2016-03-13 23:41:18 +00:00
(evil-insert-state))
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
(defun spacemacs/fsharp-eval-region-focus (start end)
"Send the current phrase to REPL and switch to the REPL in
`insert state'."
(interactive "r")
(fsharp-eval-region start end)
(switch-to-buffer-other-window inferior-fsharp-buffer-name)
Use evil in holy-mode Motivation While disabling Evil in holy-mode makes its implementation shorter and sounds elegant on the paper, in practice it puts a big burden on the configuration parts which need to know if Evil is enable or not. This is a bad separation of concerns and the bunch of fixes that we were forced to do in the past weeks shows this issue. Those fixes were about removing the knowledge of the activation of Evil by implementing new dispatching functions to be used by layers, this is cumbersome and makes Spacemacs layer configuration more subtle which is not good. There was additional bad consequences of the removal of Evil state like the impossibility to use Evil lisp state or iedit states, or we would have been forced to implement a temporary activation of Evil which is awkward. Instead I reintroduce Evil as the central piece of Spacemacs design thus Evil is now re-enabled in holy-mode. It provides the abstraction we need to isolate editing styles and be able to grow the Spacemacs configuration coverage sanely. Layers don't need to check whether the holy mode is active or not and they don't need to know if Evil is available (it is always available). We also don't need to write additional dispatching functions, this is the job of Evil, and I think it provides everything for this. Ideally configuration layer should be implemented with only Evil in mind and the holy-mode (and hybrid-mode) should magically make it work for Emacs style users, for instance we can freely use `evil-insert-state` anywhere in the code without any guard. Evil is now even more part of Spacemacs, we can really say that Spacemacs is Emacs+Evil which is now an indivisible pair. Spacemacs needed this stable API to continue on the right track. While these changes should be rather transparent to the user, I'm sorry for this experimental period, I failed to see all the implications of such a change, I was just excited about the possibility to make Evil optional. The reality is that Spacemacs has to embrace it and keep its strong position on being Emacs+Evil at the core. Implementation - insert, motion and normal states are forced to emacs state using an advice on `evil-insert-state`, `evil-motion-state` and `evil-normal-state` respectively. These functions can be used freely in the layer configuration. - A new general hook `spacemacs-editing-style-hook` allow to hook any code that need to be configured based on the editing style. Functions hooked to this hook takes the current style as parameter, this basically generalize the hook used to setup hjkl navigation bindings. - ESC has been removed from the emacs state map. - Revert unneeded changes - Revert "evil: enter insert-state only from normal-state" commit bdd702dfbe302206bbc989c7a0832daba087a781. - Revert "avoid being evil in deft with emacs editing style" commit f3a16f49ed27cc8cf05f23f93b006d6e04235381. Additional changes All editing style packages have been moved to a layer called `spacemacs-editing-styles` Notes I did not have time to attack hybrid mode, I should be able to do it later.
2016-03-13 23:41:18 +00:00
(evil-insert-state))
Adapt fsharp to the conventions
2015-03-14 05:45:52 +00:00
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
(spacemacs/declare-prefix-for-mode 'fsharp-mode "ms" "repl")
added prefixes to the fsharp layer
2017-09-24 16:50:49 +00:00
(spacemacs/declare-prefix-for-mode 'fsharp-mode "mc" "compile")
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
(unless (eq (spacemacs//fsharp-backend) 'lsp)
(spacemacs/declare-prefix-for-mode 'fsharp-mode "mg" "goto"))
added prefixes to the fsharp layer
2017-09-24 16:50:49 +00:00
layers: Transition to new key bindings functions Removes dependence on evil-leader centralizing control over the method of key binding in core-keybindings.el
2015-11-18 00:38:05 +00:00
(spacemacs/set-leader-keys-for-major-mode 'fsharp-mode
"cc" 'compile
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
"ga" 'fsharp-find-alternate-file
layers: Transition to new key bindings functions Removes dependence on evil-leader centralizing control over the method of key binding in core-keybindings.el
2015-11-18 00:38:05 +00:00
"sb" 'fsharp-load-buffer-file
"sB" 'spacemacs/fsharp-load-buffer-file-focus
"si" 'fsharp-show-subshell
"sp" 'fsharp-eval-phrase
"sP" 'spacemacs/fsharp-eval-phrase-focus
"sr" 'fsharp-eval-region
"sR" 'spacemacs/fsharp-eval-region-focus
[fsharp] Add LSP support
2020-11-09 21:21:30 +00:00
"'" 'fsharp-show-subshell))))
Expand gtags use to many more languages
2016-04-05 04:08:34 +00:00
(defun fsharp/post-init-ggtags ()
Further improve gtags layer - Add option to disable by default - Use local-vars hook to allow per-project enable/disable - Don’t enable helm-gtags-mode (no need) - Move emacs bindings from helm-gtags-mode-map to ggtags-mode-map
2016-08-15 19:24:44 +00:00
(add-hook 'fsharp-mode-local-vars-hook #'spacemacs/ggtags-mode-enable))
Expand gtags use to many more languages
2016-04-05 04:08:34 +00:00
Add ivy support to the gtags layer It would be much better to have a single function for each layer that initializes ggtags, helm-gtags and counsel-gtags for a mode.
2017-08-26 21:18:09 +00:00
(defun fsharp/post-init-counsel-gtags ()
(spacemacs/counsel-gtags-define-keys-for-mode 'fsharp-mode))
Expand gtags use to many more languages
2016-04-05 04:08:34 +00:00
(defun fsharp/post-init-helm-gtags ()
(spacemacs/helm-gtags-define-keys-for-mode 'fsharp-mode))
Reference in a new issue Copy permalink