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?

  • varsderk@alien.topOPBEnglish
    1·
    11 months ago

    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.

    • varsderk@alien.topOPBEnglish
      1·
      11 months ago

      Oooooooooohhhhhhhhhh… I can run things like cal or julia and it handles all the escape codes seamlessly. Wow. Totally sold now.

      • nemoniac@alien.topBEnglish
        1·
        11 months ago

        Any tips on how to deal with $TERM being eat-truecolor? It confuses some apps, e.g. julia is monocolor

        • varsderk@alien.topOPBEnglish
          1·
          11 months ago

          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))