>>854805
This is actually true of me except unironically. I haven't touched the bash prompt in what has to be years, nor have I touched any of bash's incestuous cousins, fish and zsh. It actually took me a while to realize that I didn't have much of a reason to script in bash anymore other than the fact that I liked to, since I could get away with using far superior scripting languages to far better ends. I use eshell, which is still, obviously, superficially comparable to bash, but, the thing is, eshell is an actual, literal mode within bash, and everything you do through eshell goes through emacs' tiny C core and is communicated directly to the kernel and filesystem, the same way you might with any other shell. Except it's better than a shell, because I can interface with it the same way I can with any other emacs buffer; e.g. I can use modes like smartparens and they don't fuck up. Helm-eshell-history is fantastic. Once you get a taste of what it's like to incorporate a sophisticated incremental completion and selection narrowing framework like helm into your tab completion, it makes Zsh's tab completion look like a fucking joke. Their plugins ecosystem? Child's play. I don't have to deal with the autism that is cutting and pasting to and from the clipboard by proxy of a stupid terminal emulator--all the text in my clipboard gets pooled into the Emacs killring (that I can interface with via helm-yank, by the way) automatically--not that it matters, since Emacs is my window manager, so I do everything in Emacs anyway. Oh, and did I also mention that eshell can emulate fish's syntax highlighting and autosuggestions?