> On Sat, 18 May 1996, Jell-O wrote:
> <snip>
> 
> If I knew the ansi color sequence dealing with inverse video, I could
> prescribe a patch that would set normal video every time bash prompted
> you.  It wouldn't be too hard.  I forget where you'd stick it in the
> source, but I could certainly check, if you'd like.

There is an argument that all history editing should be done at the terminal
driver level (on top of canonical mode and all that)

For bash and ksh, you can sort of fix inverse problems by having
'\e[m' (where \e is escape char) in either $PS1 or $PROMPT_COMMAND (bash only?)
Thats the escape sequence for putting vt100s and xterms back into `normal' text
mode. You can read more about it from xterm's ctlseqs file (archie for it, or 
use ftp://suphys.physics.su.oz.au/XFree86/3.1.1/untarred/xc/doc/hardcopy/xterm/ctlseqs.PS.Z)

bash has a nasty problem of not being able to edit lines >80 chars long in 
windows >80 chars wide; but then again i havent got the latest and greatest
yet

d