Subject: display problem with vesafb, TERM=vt220 and bash
To: None <>
From: Jukka Salmi <>
List: current-users
Date: 11/07/2007 18:10:39

I'm seeing this problem on a NetBSD/i386 4.99.34 system using vesafb(4)
when running bash with TERM set to `vt220',`wsvt25' or similar. I'll
try to describe how to reproduce the problem (the caret (^) indicates
the cursor position):

- Start with an empty command line (in either vi or emacs mode):


- Type `foo bar':

$ foo bar

- Move cursor back onto `b'

$ foo bar

- Hit erase (which is ^? here, generated by "Backspace" using default
  wscons mapping of keycode 14 to `Delete'):

$ fooar
(instead of `foobar'!)

- Clear screen to redraw command line (Ctrl-L):

$ foobar

- Type space:

$ foo bbar
(instead of `foo bar'!)

- Clear screen to redraw command line (Ctrl-L):

$ foo bar

I'm not sure who's the culprit. However, the problem disappears if I
do at least one of the following:

- don't use vesafb(4), i.e. use `wsdisplay0 at vga0' instead of
  `wsdisplay0 at vesafb0'
- set TERM to `vt100' instead of `vt220'
- use NetBSD's ksh instead of bash (from pkgsrc)

Is anybody able to reproduce this problem? Or is this working as
expected for anybody when using vesafb, vt220 and bash?

TIA, Jukka

bashian roulette:
$ ((RANDOM%6)) || rm -rf ~