doomemacs/modules/lang/solidity/config.el

;;; lang/solidity/config.el -*- lexical-binding: t; -*-

;;
;; Packages

;;;###package solidity-mode
(setq solidity-comment-style 'slash)


(use-package! solidity-flycheck  ; included with solidity-mode
  :when (featurep! :tools flycheck)
  :after solidity-mode
  :config
  (setq flycheck-solidity-solc-addstd-contracts t)
  (when (funcall flycheck-executable-find solidity-solc-path)
    (add-to-list 'flycheck-checkers 'solidity-checker nil #'eq))
  (when (funcall flycheck-executable-find solidity-solium-path)
    (add-to-list 'flycheck-checkers 'solium-checker nil #'eq)))


(use-package! company-solidity
  :when (featurep! :completion company)
  :after solidity-mode
  :config
  (delq! 'company-solidity company-backends)
  (set-company-backend! 'solidity-mode 'company-solidity))
Add Solidity Add basic Solidity module 2018-05-17 21:00:30 -05:00			`;;; lang/solidity/config.el -- lexical-binding: t; --`

			`;;`
Remove third line in section headers This is truly important stuff. We've saved many lives with this update. 2018-09-07 19:36:16 -04:00			`;; Packages`
Add Solidity Add basic Solidity module 2018-05-17 21:00:30 -05:00
General refactor & cleanup, across the board 2019-09-13 21:59:03 -04:00			`;;;###package solidity-mode`
Fix solium error preventing solidity-mode #659 Now conditionally activates flycheckers using the existence of their binaries at load time. 2018-06-07 18:03:58 +02:00			`(setq solidity-comment-style 'slash)`
Add Solidity Add basic Solidity module 2018-05-17 21:00:30 -05:00

:boom: Rename def-package! -> use-package! Calling this pivotal macro "def-package!" has frequently been a source of confusion. It is a thin wrapper around use-package, and it should be obvious that it is so. For this reason, and to match the naming convention used with other convenience macros/wrappers, it is now use-package!. Also changes def-package-hook! -> use-package-hook! The old macros are now marked obsolete and will be removed when straight integration is merged. 2019-07-23 12:44:03 +02:00			`(use-package! solidity-flycheck ; included with solidity-mode`
feature/{syntax-checker,spellcheck} -> tools/fly{check,spell} 2019-02-22 00:20:29 -05:00			`:when (featurep! :tools flycheck)`
lang/solidity: conform to Doom conventions 2018-05-25 19:04:01 +02:00			`:after solidity-mode`
Fix solium error preventing solidity-mode #659 Now conditionally activates flycheckers using the existence of their binaries at load time. 2018-06-07 18:03:58 +02:00			`:config`
			`(setq flycheck-solidity-solc-addstd-contracts t)`
			`(when (funcall flycheck-executable-find solidity-solc-path)`
			`(add-to-list 'flycheck-checkers 'solidity-checker nil #'eq))`
			`(when (funcall flycheck-executable-find solidity-solium-path)`
			`(add-to-list 'flycheck-checkers 'solium-checker nil #'eq)))`

Add Solidity Add basic Solidity module 2018-05-17 21:00:30 -05:00
:boom: Rename def-package! -> use-package! Calling this pivotal macro "def-package!" has frequently been a source of confusion. It is a thin wrapper around use-package, and it should be obvious that it is so. For this reason, and to match the naming convention used with other convenience macros/wrappers, it is now use-package!. Also changes def-package-hook! -> use-package-hook! The old macros are now marked obsolete and will be removed when straight integration is merged. 2019-07-23 12:44:03 +02:00			`(use-package! company-solidity`
Add Solidity Add basic Solidity module 2018-05-17 21:00:30 -05:00			`:when (featurep! :completion company)`
			`:after solidity-mode`
			`:config`
General refactor & cleanup, across the board 2019-09-13 21:59:03 -04:00			`(delq! 'company-solidity company-backends)`
Introduce autodefs to replace some settings + :popup -> set-popup-rule! + :popups -> set-popup-rules! + :company-backend -> set-company-backend! + :evil-state -> set-evil-initial-state! I am slowly phasing out the setting system (def-setting! and set!), starting with these. What are autodefs? These are functions that are always defined, whether or not their respective modules are enabled. However, when their modules are disabled, they are replaced with macros that no-op and don't waste time evaluating their arguments. The old set! function will still work, for a while. 2018-06-15 02:58:12 +02:00			`(set-company-backend! 'solidity-mode 'company-solidity))`