[Emacs-diffs] master c09116e: Remove an opinionated section on "What Eshell is not"

[John Wiegley]

branch: master
commit c09116e64012534ee244c22f1ba4f2e106f6ed91
Author: John Wiegley <address@hidden>
Commit: John Wiegley <address@hidden>

    Remove an opinionated section on "What Eshell is not"
    
    I don't find this information to accurately reflect possible use cases
    for Eshell; plus, it doesn't offer much in the way of information,
    just opinion.
---
 doc/misc/eshell.texi | 18 ------------------
 1 file changed, 18 deletions(-)

diff --git a/doc/misc/eshell.texi b/doc/misc/eshell.texi
index a7651b2..8963826 100644
--- a/doc/misc/eshell.texi
+++ b/doc/misc/eshell.texi
@@ -142,24 +142,6 @@ Any tool you use often deserves the time spent learning to 
master it.
 looks like: But don't let it fool you; once you know what's going on,
 it's easier than it looks: @code{ls -lt **/*.doc(Lk+50aM+5)}.}
 
address@hidden What Eshell is not
address@hidden Eshell, what it is not
address@hidden what Eshell is not
address@hidden what isn't Eshell?
-
-Eshell is @emph{not} a replacement for system shells such as
address@hidden or @command{zsh}.  Use Eshell when you want to move
-text between Emacs and external processes; if you only want to pipe
-output from one external process to another (and then another, and so
-on), use a system shell, because Emacs's IO system is buffer oriented,
-not stream oriented, and is very inefficient at such tasks.  If you
-want to write shell scripts in Eshell, don't; either write an elisp
-library or use a system shell.
-
-Some things Eshell just doesn't do well.  It fills the niche between
-IELM and your system shell, where the peculiar use-cases lie, and it
-is less than ideal outside that niche.
-
 @menu
 * Contributors to Eshell::      People who have helped out!
 @end menu