> 1) Why is lynx completely useless with TERM=xterm (full-on blank
> white). Will recompiling it fix this? (I doubt it, since I'm pretty
> sure I built it *after* installing 1.5 and its new termcaps on this
> laptop).

This I don't understand.  Can you send me the lynx screen output please
(something like `lynx > lynx.out`, then type 'q' and 'y')?  I might be
able to work out what's happening here.

> 2) Why, oh why will my xterms not listen to the +vb flag? Or the
> XTerm*visualBell: false setting in my .Xdefaults? I'm X forwarding
> over a DSL connection. I assure you I do *not* want my screen to
> flash every damn time vi beeps.

See PR 11882.  Install r1.64 of src/share/termcap/termcap.src or apply
the attached patch and that should solve this problem.  This patch has
been pulled up to the 1.5 branch.

J

-- 
                    My other computer also runs NetBSD
                          http://www.netbsd.org/

 ---8<---------------------------- Cut here ---------------------------->8---

Index: sharesrc/share/termcap/termcap.src
diff -u sharesrc/share/termcap/termcap.src:1.63 sharesrc/share/termcap/termcap.src:1.64
--- sharesrc/share/termcap/termcap.src:1.63	Sun Oct 22 22:29:46 2000
+++ sharesrc/share/termcap/termcap.src	Sun Jan 14 21:10:59 2001
@@ -1,4 +1,4 @@
-#	$NetBSD: termcap.src,v 1.63 2000/10/22 19:29:46 scottr Exp $
+#	$NetBSD: termcap.src,v 1.64 2001/01/14 19:10:59 jdc Exp $
 #
 ######## TERMINAL TYPE DESCRIPTIONS SOURCE FILE
 #
@@ -1781,8 +1781,13 @@
 	:u6=\E[%i%d;%dR:u7=\E[6n:u8=\E[?1;2c:u9=\E[c:\
 	:tc=xterm-r6:
 
-# This is the standard xterm entry.
+# This is the standard xterm entry.  Visual bell is undefined for compatibility
+# with older implementations.
 xterm|vs100|xterms|xterm terminal emulator (X Window System):\
+	:vb@:tc=xterm-xf86-v33:
+
+# Xterm with the visual bell capability.
+xterm-vb|xterm terminal emulator with visual bell:\
 	:tc=xterm-xf86-v33:
 
 # These entries allow access to the X titlebar and icon name as a status line.