Eat-eshell-mode turns the eshell buffer itself into an eat terminal. Since top
is in eshell-visual-commands
list, it gets run in a separate term mode buffer. To switch this out for an eat buffer, use eat-eshell-visual-command-mode
.
this post was submitted on 17 Oct 2023
2 points (100.0% liked)
Emacs
314 readers
2 users here now
A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
Get Emacs
Rules
- Posts should be emacs related
- Be kind please
- Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.
Emacs Resources
Emacs Tutorials
- Beginner’s Guide to Emacs
- Absolute Beginner's Guide to Emacs
- How to Learn Emacs: A Hand-drawn One-pager for Beginners
Useful Emacs configuration files and distributions
Quick pain-saver tip
founded 1 year ago
MODERATORS
Thank you! That's helpful. I'm a little confused: what benefit does turning the eshell buffer into an eat terminal give you? Better perf? I'm still new to eshell and stuff.
Oooooooooohhhhhhhhhh… I can run things like cal
or julia
and it handles all the escape codes seamlessly. Wow. Totally sold now.
This exactly. For me it's neofetch
this is why I'm so hype about it lol
Any tips on how to deal with $TERM being eat-truecolor? It confuses some apps, e.g. julia is monocolor
This is my current config: set TERM to "xterm", and fix the otherwise impossible-to-see ANSI blue:
(use-package eat
:custom
(eat-term-name "xterm")
:custom-face
(ansi-color-bright-blue ((t (:foreground "#00afff" :background "#00afff"))))
:config
(evil-set-initial-state 'eat-mode 'emacs)
(eat-eshell-mode)
(eat-eshell-visual-command-mode))