^[[1m and More When Shelling Out in emacs

Is your PS1 variable set to be bold, with white text on red background? Change it to contain no colors (control codes) at all.

Hi,

Will you try to set your TERM varibale? such as:

export TERM=linux

and try to run emacs after setting the shell variable.

Cheers,
K.

May be you'd likte to see what it is set in your environment. Please execute env and post the output here.

which TERM environment variable have you set in your (remote) shell?
which putty settings do you have for Windows->Colours?

I have pasted in my env below. I understand now that the codes are color escape codes and, yes, my prompt is white on red. Removing the color does indeed remove the escape codes from the Emacs shell window.

If you are saying I cannot have a colorized prompt without having the escape codes appear in an Emacs shell window, I can remove the color permanently, but I am unclear as to why the Emacs shell window would not understand and handle it like my BASH shell does.

Many thanks,

TERM=xterm
SHELL=/bin/bash
XDG_SESSION_COOKIE=3b72570aa705097c7f5e7777490a2956-1243703209.726674-1567315895
SSH_CLIENT=192.168.1.102 4495 22
SSH_TTY=/dev/pts/2
USER=user
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.svgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:
MAIL=/var/mail/user
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
PWD=/home/user
LANG=en_US.UTF-8
HISTCONTROL=ignoreboth
SHLVL=1
HOME=/home/user
LOGNAME=user
SSH_CONNECTION=192.168.1.102 4495 192.168.1.105 22
LESSOPEN=| /usr/bin/lesspipe %s
DISPLAY=localhost:11.0
LESSCLOSE=/usr/bin/lesspipe %s %s
_=/usr/bin/env
OLDPWD=/usr/lib/python2.5/site-packages/scapy

Hi,

The  reason is simple. You have created the red on white backgroud effect using the Escape sequences for a terminal type. But Xterm and Vi have different databases to query the terminal capabilties and they don't match.

You would either set your terminal  type to xterm-color (export TERM=xtaer-color)
or
you would prevent vi to use escape sequences. (export LESS="-X" in tyour .bash_profile)

Cheers,
K.

Perfect. Thanks so much. Never thought to google using ANSI and color keywords for what looked like gibberish to me in the shell window.

Opps sorry TERM=xtaer-color should read TERM=xterm-color