3 ms·

> What I find more important however is the effective window/buffer management. Yes! I cannot imagine how my life looked before `C-x b` (switch buffers in helm

> What I find more important however is the effective window/buffer management. Yes! I cannot imagine how my life looked before `C-x b` (switch buffers in helm). However, I still have an actual terminal emulator open the entire time for serious stuff. Eshell is not compatible with a lot of programs, term/ansiterm are ok but not quite as good as a dedicated terminal. I get around having to context switch by using virtual desktops (KDE). I have Shift-F1 bound to the desktop with only emacs, and Shift-F3 to my terminal. Works beautifully. Rather than try to use a terminal in emacs I've found it more useful to use an solution designed for emacs, i.e git vs magit.

smabie 6y ago
Eshell is a really great shell and a lot of full screen nurses apps can be replaced with an Emacs equivalent. The ability to use elisp in pipes and stuff is a game changer
- JoelMcCracken 6y ago
  I’ve never been able to make eshell part of my workflow. I wonder if you would share more info
  - smabie 6y ago
    Sure, so basically I keep a small eshell window at the bottom of my current frame at all times. Full screen commands like man, info, or less will automatically open a new Emacs buffer. You can seamlessly mix and match shell constructs and elisp, allowing you to leverage elisp and traditional shell scripting together. It also makes it really easy to open a file from eshell since you're already in Emacs. Instead of things like top, I just use Emacs process viewer. For full screen apps that absolutely have no Emacs equivalent (quite rare), I have a term buffer that I occasionally use. You should check out a list of eshell features, its much more powerful than even zsh. Also I use company-mode for command and file completion, which is a lot nicer than zsh 's completion method, for example. Once you get used eshell, it's hard to go back. I think you should be able to use eshell+Emacs for almost everything, and for me at least, I find the experience quite nice.
deleted 6y ago
[deleted]
JoelMcCracken 6y ago
I used both of those for years but recently switched to vterm. I highly recommend it. I do keep a terminal open for a variety of reasons (and some curses apps don’t work perfectly in emacs) but I probably only use it every other work day.

smabie 6y ago

Eshell is a really great shell and a lot of full screen nurses apps can be replaced with an Emacs equivalent. The ability to use elisp in pipes and stuff is a game changer

JoelMcCracken 6y ago
I’ve never been able to make eshell part of my workflow. I wonder if you would share more info
- smabie 6y ago
  Sure, so basically I keep a small eshell window at the bottom of my current frame at all times. Full screen commands like man, info, or less will automatically open a new Emacs buffer. You can seamlessly mix and match shell constructs and elisp, allowing you to leverage elisp and traditional shell scripting together. It also makes it really easy to open a file from eshell since you're already in Emacs. Instead of things like top, I just use Emacs process viewer. For full screen apps that absolutely have no Emacs equivalent (quite rare), I have a term buffer that I occasionally use. You should check out a list of eshell features, its much more powerful than even zsh. Also I use company-mode for command and file completion, which is a lot nicer than zsh 's completion method, for example. Once you get used eshell, it's hard to go back. I think you should be able to use eshell+Emacs for almost everything, and for me at least, I find the experience quite nice.

deleted 6y ago

[deleted]

JoelMcCracken 6y ago

I used both of those for years but recently switched to vterm. I highly recommend it. I do keep a terminal open for a variety of reasons (and some curses apps don’t work perfectly in emacs) but I probably only use it every other work day.