IMPORTANT: This is a breaking update for Mac users, as your shell environment will no longer be inherited correctly (with the removal of exec-path-from-shell). The quick fix is: 'bin/doom env refresh'. Also, the set-env! autodef now does nothing (and is deprecated), be sure to remove calls to it in your config. Smaller changes: + This update also adds --no-* switches to doom quickstart + Includes general improvements to the documentation of several bin/doom commands. + Moves doom/reload* commands to core/autoload/config.el + doom/reload-project has been removed (it didn't actually do anything) The breaking change: This update adds an "envvar file" to Doom Emacs. This file is generated by `doom env refresh`, populated with variables scraped from your shell environment (from both non-interactive and interactive sessions). This file is then (inexpensively) loaded at startup, if it exists. + The file is manually generated with `doom env refresh`. + It can be regenerated automatically whenever `doom refresh` is run by running `doom env enable` (`doom env clear` will reverse this and delete the env file). + `doom quickstart` will ask if you want to auto-generate this envvar file. You won't need it if you're confident Emacs will always be started from the correct environment, however. + Your env file can be reloaded from a running Emacs session with `M-x doom/reload-env`. Note: this won't work if the Emacs session you're running it in doesn't have a correct SHELL set. i.e. don't use this to create your first env file! The idea isn't mine -- it's borrowed from Spacemacs -- and was introduced to me in #1053 by @yurimx. I was impressed with it. Prior to this, I was unhappy with exec-path-from-shell (no hate to the dev, I understand its necessity), and 'doom patch-macos' wasn't ideal for mac users (needed to be reapplied every time you update Emacs). What's more, many users (even Linux users) had to install exec-path-from-shell anyway. This solution suffers from none of their shortcomings. More reliable than patch-macos, more performant and complete than exec-path-from-shell, and easily handled by bin/doom.
40 lines
1.8 KiB
EmacsLisp
40 lines
1.8 KiB
EmacsLisp
;;; tools/vterm/config.el -*- lexical-binding: t; -*-
|
|
|
|
(def-package! vterm
|
|
:when (fboundp 'module-load)
|
|
:defer t
|
|
:preface (setq vterm-install t)
|
|
:config
|
|
(set-popup-rule! "^vterm" :size 0.25 :vslot -4 :select t :quit nil :ttl 0)
|
|
|
|
(add-hook 'vterm-mode-hook #'doom|mark-buffer-as-real)
|
|
;; Automatically kill buffer when vterm exits.
|
|
(add-to-list 'vterm-exit-functions (lambda (buffer) (if buffer (kill-buffer buffer))))
|
|
|
|
(when (featurep! :feature evil)
|
|
(evil-set-initial-state 'vterm-mode 'insert)
|
|
;; Go back to normal state but don't move cursor backwards. Moving cursor
|
|
;; backwards is the default Vim behavior but it is not appropriate in some
|
|
;; cases like terminals.
|
|
(setq-hook! 'vterm-mode-hook evil-move-cursor-back nil)
|
|
;; Those keys are commonly needed by terminals.
|
|
(evil-define-key* 'insert vterm-mode-map
|
|
(kbd "C-a") #'vterm--self-insert
|
|
(kbd "C-b") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-d") #'vterm--self-insert
|
|
(kbd "C-e") #'vterm--self-insert
|
|
(kbd "C-f") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-k") #'vterm--self-insert
|
|
(kbd "C-l") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-n") #'vterm--self-insert
|
|
(kbd "C-o") #'vterm--self-insert
|
|
(kbd "C-p") #'vterm--self-insert
|
|
(kbd "C-q") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-r") #'vterm--self-insert
|
|
(kbd "C-s") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-t") #'vterm--self-insert
|
|
(kbd "C-u") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-v") #'vterm--self-insert ; Should not be necessary.
|
|
(kbd "C-w") #'vterm--self-insert
|
|
(kbd "C-y") #'vterm--self-insert
|
|
(kbd "C-z") #'vterm--self-insert)))
|