emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
doomemacs/modules/tools/direnv/config.el

38 lines
1.7 KiB
EmacsLisp
Raw Normal View History

Add tools/direnv module
2019-04-05 03:16:37 -04:00
;;; tools/direnv/config.el -*- lexical-binding: t; -*-
tools/direnv: replace direnv package with envrc wbolster/emacs-direnv uses an approach that mutates global state, allowing a direnv to bleed into unrelated buffers and contexts. For this to work it must rereads the direnv every time you switch buffers, which can be very slow. purcell/envrc, on the other hand, makes env state buffer-local, so the direnv only needs to be read once, when a is first initialized. This is faster and less error prone. However, it's necessary to manually reload the direnv if you've changed your .envrc outside of Emacs (with `M-x envrc-reload` or `M-x envrc-reload-all`).
2020-08-21 02:34:07 -04:00
(use-package! envrc
:when (executable-find "direnv")
tools/direnv: refactor Our advice is no longer needed, now that envrc provides envrc-propagate-environment. We also cache the executable path (benefits TRAMP users, in particular).
2021-07-06 02:19:05 -04:00
:hook (doom-first-file . envrc-global-mode)
Add tools/direnv module
2019-04-05 03:16:37 -04:00
:config
tools/direnv: replace direnv package with envrc wbolster/emacs-direnv uses an approach that mutates global state, allowing a direnv to bleed into unrelated buffers and contexts. For this to work it must rereads the direnv every time you switch buffers, which can be very slow. purcell/envrc, on the other hand, makes env state buffer-local, so the direnv only needs to be read once, when a is first initialized. This is faster and less error prone. However, it's necessary to manually reload the direnv if you've changed your .envrc outside of Emacs (with `M-x envrc-reload` or `M-x envrc-reload-all`).
2020-08-21 02:34:07 -04:00
(add-to-list 'doom-debug-variables 'envrc-debug)
tools/direnv: fontify direnv stdlib keywords
2019-07-10 02:29:13 +02:00
Add popup rule for *envrc* error buffers
2021-05-12 16:28:52 -04:00
(set-popup-rule! "^\\*envrc\\*" :quit t :ttl 0)
Drop Emacs 26.x support Emacs 27.x has been the stable version of Emacs for nearly a year, and introduces a litany of bugfixes, performance, and quality-of-life improvements that significantly reduce Doom's maintenance burden (like XDG support, early-init.el, image manipulation without imagemagick, a native JSON library, harfbuzz support, pdumper, and others). With so many big changes on Doom's horizon, I like having one less (big) thing to worry about. Also reverts bb677cf7a (#5232) as it is no longer needed.
2021-07-06 01:54:32 -04:00
;; A globalized minor mode triggers on `after-change-major-mode-hook'
;; normally, which runs after a major mode's body and hooks. If those hooks do
;; any initialization work that's sensitive to environmental state set up by
;; direnv, then you're gonna have a bad time, so I move the trigger to
;; `change-major-mode-after-body-hook' instead. This runs before said hooks
;; (but not the body; fingers crossed that no major mode does important env
;; initialization there).
(add-hook! 'envrc-global-mode-hook
(defun +direnv-init-global-mode-earlier-h ()
(let ((fn #'envrc-global-mode-enable-in-buffers))
(if (not envrc-global-mode)
(remove-hook 'change-major-mode-after-body-hook fn)
(remove-hook 'after-change-major-mode-hook fn)
(add-hook 'change-major-mode-after-body-hook fn 100)))))
tools/direnv: only run direnv once per buffer Halves the time direnv integration takes to initialize.
2020-11-10 16:29:13 -05:00
Revert direnv modifications Not worth the trouble. I'll move it to my private config. Fixes #2384 Closes #2384
2020-02-02 03:18:49 -05:00
(defadvice! +direnv--fail-gracefully-a (&rest _)
"Don't try to use direnv if the executable isn't present."
tools/direnv: replace direnv package with envrc wbolster/emacs-direnv uses an approach that mutates global state, allowing a direnv to bleed into unrelated buffers and contexts. For this to work it must rereads the direnv every time you switch buffers, which can be very slow. purcell/envrc, on the other hand, makes env state buffer-local, so the direnv only needs to be read once, when a is first initialized. This is faster and less error prone. However, it's necessary to manually reload the direnv if you've changed your .envrc outside of Emacs (with `M-x envrc-reload` or `M-x envrc-reload-all`).
2020-08-21 02:34:07 -04:00
:before-while #'envrc-mode
tools/direnv: refactor Our advice is no longer needed, now that envrc provides envrc-propagate-environment. We also cache the executable path (benefits TRAMP users, in particular).
2021-07-06 02:19:05 -04:00
(or (get 'envrc-mode 'direnv-executable)
(put 'envrc-mode 'direnv-executable (executable-find "direnv" t))
Fix #3812: direnv not in scope for babel execution
2020-08-23 21:37:02 -04:00
(ignore (doom-log "Couldn't find direnv executable"))))
tools/direnv: refactor Our advice is no longer needed, now that envrc provides envrc-propagate-environment. We also cache the executable path (benefits TRAMP users, in particular).
2021-07-06 02:19:05 -04:00
;; Ensure babel's execution environment matches the host buffer's.
(advice-add #'org-babel-execute-src-block :around #'envrc-propagate-environment)
;; Make sure any envrc changes are propagated after a `doom/reload'
(add-hook 'doom-after-reload-hook #'envrc-reload-all))
Reference in a new issue Copy permalink