doomemacs/modules/term/vterm/config.el

;;; term/vterm/config.el -*- lexical-binding: t; -*-

(use-package! vterm
  :when (featurep 'dynamic-modules)
  :commands vterm-mode
  :hook (vterm-mode . doom-mark-buffer-as-real-h)
  :hook (vterm-mode . hide-mode-line-mode) ; modeline serves no purpose in vterm
  :preface
  ;; HACK Because vterm clusmily forces vterm-module.so's compilation on us when
  ;;      the package is loaded, this is necessary to prevent it when
  ;;      byte-compiling this file (`use-package' blocks eagerly loads packages
  ;;      when compiled).
  (when noninteractive
    (advice-add #'vterm-module-compile :override #'ignore)
    (provide 'vterm-module))

  :config
  (set-popup-rule! "^\\*vterm" :size 0.25 :vslot -4 :select t :quit nil :ttl 0)

  ;; Once vterm is dead, the vterm buffer is useless. Why keep it around? We can
  ;; spawn another if want one.
  (setq vterm-kill-buffer-on-exit t)

  ;; 5000 lines of scrollback, instead of 1000
  (setq vterm-max-scrollback 5000)

  (setq-hook! 'vterm-mode-hook
    ;; Don't prompt about dying processes when killing vterm
    confirm-kill-processes nil
    ;; Prevent premature horizontal scrolling
    hscroll-margin 0))
Move eshell, term & vterm modules to :term 2019-05-18 23:41:18 -04:00			`;;; term/vterm/config.el -- lexical-binding: t; --`
Add vterm layer vterm layer uses emacs-libvterm for terminal support 2019-01-27 03:45:29 +08: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! vterm`
refactor: deprecate EMACS2[89]+, NATIVECOMP, MODULES To reduce redundancy, remove the maintenance hassle that version constants would impose later on, and rely on built-in facilities (featurep) more over global variables or doomisms, these global constants have been deprecated in favor of Emacs "features": - EMACS28+ -- replace with (> emacs-major-version 27) - EMACS29+ -- replace with (> emacs-major-version 28) - NATIVECOMP -- replace with (featurep 'native-compile) - MODULES -- replace with (featurep 'dynamic-modules) (These constants will be formally removed when v3 is released. The IS-* constants are likely next, but I haven't decided on their substitutes yet) I also decided to follow native-compile's example and provide features for Emacs' system features (since system-configuration-features' docs outs itself as a poor method to detect features): - dynamic-modules - jansson - native-compile -- this one already exists, but will instead be removed if it's non-functional; i.e. (native-comp-available-p) returns nil. These are now detectable using featurep, which is fast and built-in. 2022-08-12 20:07:08 +02:00			`:when (featurep 'dynamic-modules)`
Bump :term vterm akermu/emacs-libvterm@01a1332 -> akermu/emacs-libvterm@101ff86 2020-11-25 12:33:53 -05:00			`:commands vterm-mode`
Refactor vterm module 2020-04-23 16:53:37 -04:00			`:hook (vterm-mode . doom-mark-buffer-as-real-h)`
			`:hook (vterm-mode . hide-mode-line-mode) ; modeline serves no purpose in vterm`
nit: minor refactors & comment/docstring revisions 2022-06-21 14:40:15 +02:00			`:preface`
Don't build vterm-module in noninteractive sessions Fixes 'doom compile' when :term vterm is enabled. Mentioned in #5086 2021-05-24 13:54:13 -04:00			`;; HACK Because vterm clusmily forces vterm-module.so's compilation on us when`
			`;; the package is loaded, this is necessary to prevent it when`
			;; byte-compiling this file (`use-package' blocks eagerly loads packages
			`;; when compiled).`
			`(when noninteractive`
			`(advice-add #'vterm-module-compile :override #'ignore)`
			`(provide 'vterm-module))`

Add vterm layer vterm layer uses emacs-libvterm for terminal support 2019-01-27 03:45:29 +08:00			`:config`
Fix vterm popup rule akermu/emacs-libvterm@c2c2c8afb935c11778388721912250cd1103aaf9 changed the default buffer name of vterm buffers, so Doom's popup-rule no longer matches them. This causes functions like `+vterm/here` to use the entire frame instead of creating a popup window. Fix it by changing the popup rule to match the new naming scheme. 2021-04-10 19:15:11 +10:00			`(set-popup-rule! "^\\*vterm" :size 0.25 :vslot -4 :select t :quit nil :ttl 0)`
Lazy-load vterm & refactor config 2019-02-18 18:56:20 -05:00
Refactor vterm module 2020-04-23 16:53:37 -04:00			`;; Once vterm is dead, the vterm buffer is useless. Why keep it around? We can`
			`;; spawn another if want one.`
			`(setq vterm-kill-buffer-on-exit t)`

vterm-max-scrollback = 5000 2020-11-04 15:22:58 -05:00			`;; 5000 lines of scrollback, instead of 1000`
			`(setq vterm-max-scrollback 5000)`

Prevent premature h-scrolling in vterm buffers 2020-01-12 20:05:26 -05:00			`(setq-hook! 'vterm-mode-hook`
Refactor vterm module 2020-04-23 16:53:37 -04:00			`;; Don't prompt about dying processes when killing vterm`
Prevent premature h-scrolling in vterm buffers 2020-01-12 20:05:26 -05:00			`confirm-kill-processes nil`
			`;; Prevent premature horizontal scrolling`
Bump evil-collection, vterm emacs-evil/evil-collection@ffbf149 -> emacs-evil/evil-collection@e6824e2 akermu/emacs-libvterm@101ff86 -> akermu/emacs-libvterm@fb12d7f Closes #4591 Co-authored-by: Michael Lingelbach <mjlbach@users.noreply.github.com> 2021-01-30 17:57:45 -05:00			`hscroll-margin 0))`