doomemacs/modules/lang/hy/config.el

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

(def-package! hy-mode
  :mode "\\.hy\\'"
  :interpreter "hy"
  :config
  (set! :repl 'hy-mode #'hy-shell-start-or-switch-to-shell)
  (set-company-backend! 'hy-mode 'company-hy))
lang/hy: initial commit 2017-06-24 18:07:54 +02:00			`;;; lang/hy/config.el -- lexical-binding: t; --`

			`(def-package! hy-mode`
Major refactor & optimization of how modules load their packages Now that we are loading package autoloads files (as part of the generated doom-package-autoload-file when running make autoloads), many :commands properties are redundant. In fact, many def-package! blocks are redundant. In some cases, we can do without a config.el file entirely, and can move into the autoloads file or rely entirely on package autoloads. Also, many settings have been moved in their module's autoloads files, which makes them available ASAP; their use no longer depends on module load order. This gained me a modest ~10% boost in startup speed. 2018-05-25 00:46:11 +02:00			`:mode "\\.hy\\'"`
lang/hy: set :repl, :company-backend & :interpreter 2018-02-14 07:44:23 -05:00			`:interpreter "hy"`
			`:config`
			`(set! :repl 'hy-mode #'hy-shell-start-or-switch-to-shell)`
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! 'hy-mode 'company-hy))`