Hey there,
Maybe I’m just missing something obvious, but I’m a little bit confused as to how eat-eshell-mode works. If I, for example, fire up Eshell with Eat installed:
(elpaca-test
:interactive t
:init
(elpaca eat (eat-eshell-mode))
(eshell))
Then I try running e.g. top, I’d expect top to open in an Eat buffer, but it’s not doing that for me right now: it just opens in plain ol’ dumpy Term mode.
What am I missing? Is this not what Eshell integration is supposed to do? How do you use Eshell and Eat together?
Eat-eshell-mode turns the eshell buffer itself into an eat terminal. Since
topis ineshell-visual-commandslist, it gets run in a separate term mode buffer. To switch this out for an eat buffer, useeat-eshell-visual-command-mode.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
calorjuliaand 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: