3 ms·
One thing I really like about Eshell is how you can make the whole buffer editable. Printed too many lines by accident? Just mark the whole region and do M-x de
by spain 12y ago
One thing I really like about Eshell is how you can make the whole buffer editable. Printed too many lines by accident? Just mark the whole region and do M-x delete-non-matching lines. Other fun things to do include using output redirection to insert text straight into buffers! One last cool thing is that Eshell comes with it's own little pseudo-devices like /dev/kill and /dev/clip, you can probably guess what they're for.
Although as awesome as it is, there are still some places where I have no choice but to use a real terminal. This is mostly curses-like interfaces and stuff.
I find it funny that the author omitted one of the biggest missing features in Eshell: input redirection, you just can't do it.
Here's further reading for anyone interested in Eshell, I think this is the most comprehensive little guide out there:
http://www.masteringemacs.org/article/complete-guide-mastering-eshell http://www.masteringemacs.org/article/complete-guide-masteri...
- dllthomas 12y ago"This is mostly curses-like interfaces and stuff." Which is, of course, a great example of the reason we need to provide as much functionality as we reasonably can outside such interfaces (including GUI interfaces).
- username223 12y agoI have tried to like it, but the lack of input redirection is just pathetic. Worse, rather than just calling a real shell when it detects attempted input redirection, it chastises you and refuses to do anything. Plus, while Emacs' "M-x command" completion is great, Eshell was still about as good as mid-90s Bash the last time I tried it. And then there's the cost of learning yet another slightly-different shell syntax. While this could probably be done right, it hasn't been in the 10+ years of Eshell's existence, so I'm not holding my breath.