# HG changeset patch
# User Glenn Morris <rgm@gnu.org>
# Date 1227587146 0
# Node ID c7bff6d07d9ce9bcd8830eba65fc953464c015b4
# Parent  0be1dac780bbe1098ce764354d4c368a9ec7dccd
(eshell-gather-process-output): Revert previous change.  (re-opens Bug#1388)

diff -r 0be1dac780bb -r c7bff6d07d9c lisp/eshell/esh-proc.el
--- a/lisp/eshell/esh-proc.el	Tue Nov 25 04:24:45 2008 +0000
+++ b/lisp/eshell/esh-proc.el	Tue Nov 25 04:25:46 2008 +0000
@@ -250,27 +250,11 @@
     (cond
      ((fboundp 'start-process)
       (setq proc
-	    ;; Bug#1388.  Some commands (eg bc) check isatty to decide
-	    ;; whether they are being called interactively.
-	    ;; A normal shell pipeline has:
-	    ;; first: stdin tty , stdout pipe
-	    ;; rest : stdin pipe, stdout pipe
-	    ;; last : stdin pipe, stdout tty
-	    ;; We have:
-	    ;; first: stdin tty , stdout tty
-	    ;; last : stdin pipe, stdout pipe
-	    ;; In other words, the first and last elements have the
-	    ;; wrong kind of stdout.  (Perhaps this does not matter much...)
-	    ;; FIXME which is better for the first element:
-	    ;; tty/tty (as now), or pipe/pipe?
-	    (let ((process-connection-type
-		   (unless (and eshell-in-pipeline-p
-				(not (eq eshell-in-pipeline-p 'first)))
-		     process-connection-type)))
-	      (apply 'start-process
-		     (file-name-nondirectory command) nil
-		     ;; `start-process' can't deal with relative filenames
-		     (append (list (expand-file-name command)) args))))
+	    (apply 'start-process
+		   (file-name-nondirectory command) nil
+		   ;; `start-process' can't deal with relative
+		   ;; filenames
+		   (append (list (expand-file-name command)) args)))
       (eshell-record-process-object proc)
       (set-process-buffer proc (current-buffer))
       (if (eshell-interactive-output-p)