So the only thing that keeps me from using eshell regularly as my shell is that I sometimes hit a CLI tool that wants to use all the TTY features, and that of course gets mangled by eshell.
Has anyone found a good solution for this? I can imagine, hypothetically, detecting one is about to launch one of those CLI tools and launching them in `multi-term`, but I'm not sure how I'd set that up (in particular, a pattern of running `can-eshell | must-tty | can-eshell` commands smells like it'd require some weird plumbing).
@splatt9990 @mtomczak fwiw, here's my eshell config https://github.com/kickingvegas/cclisp/blob/6c599fb873b96f8e2d9795bb9272c89fc1676797/cc-eshell-mode.el
@kickingvegas Thank you! This is extremely helpful.
@mtomczak see the variable `eshell-visual-commands`. It's a list of strings representing commands that should be run in a terminal emulator. Should help a bit.