bug#3345: eshell environment does not override TERM

[John Wiegley]

On May 21, 2009, at 2:02 PM, Bruno Haible wrote:

> When I invoke M-x eshell, subprocesses see the same TERM
> environment variable as the one from which emacs was launched.
> For example, when I launch emacs from an xterm, which has
> TERM=xterm set, then processes run from within eshell will
> see TERM=xterm as well and emit ANSI control codes for bold
> or colored output. But eshell does not interpret these control
> codes, and shows weird-looking ASCII characters instead.

This has been fixed in Emacs CVS.  Eshell now interprets many ANSI  
control codes by default.

John