From owner-freebsd-questions Mon Apr 12 12: 3:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from red.csi.cam.ac.uk (red.csi.cam.ac.uk [131.111.8.70]) by hub.freebsd.org (Postfix) with ESMTP id D4575155E6 for ; Mon, 12 Apr 1999 12:03:37 -0700 (PDT) (envelope-from bjc23@hermes.cam.ac.uk) Received: from bjc23 (helo=localhost) by red.csi.cam.ac.uk with local-smtp (Exim 2.05 #3) id 10WlxL-0005Ts-00; Mon, 12 Apr 1999 20:01:15 +0100 Date: Mon, 12 Apr 1999 20:01:15 +0100 (BST) From: Ben Cohen X-Sender: bjc23@red.csi.cam.ac.uk Reply-To: bjc23@hermes.cam.ac.uk To: Doug White Cc: questions@FreeBSD.ORG Subject: Re: Two questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Doug White wrote: >> Firstly, when using some applications, particularly vi, in an xterm under >> X the numeric keypad produces garbage like >> y >> x >> w >> v >> u >> this when I try to use it to get numbers. > >You _do_ have NumLock on, right? Yes, I do. The arrows seem to work OK when it NumLock is off. (I'm using termcap xterm-color. I have noticed similar things happen in vi and vim when using them via telnet from Windows. It could be a termcap problem.) >I've not had this problem since the 2.1.X days. I forgot to say I'm using 3.0 Release (I think) from December 1998. >> I have >> >> # Let the server do the NumLock processing. This should only be required >> # when using pre-R6 clients >> ServerNumLock >> >> in XF86Config. (This is necessary to make other applications work >> properly.) >> >> Is there any way to stop this from happening? > >Take that directive out; it makes NumLock do nutty things. If I do that then the numeric keypad doesn't work properly in other applications (other than xterm). How can I fix this? >> Secondly, kernel messages go to the console. Is there any way of >> redirecting the console to, say, /dev/ttyv2 so that when I log in on ttyv0 >> I don't get lots of messages appearing on the screen? > >No, since /dev/console is glued to that vty. Just use a different vty; we >do here. Aha. That is a pity... It's worth knowing, though. Thanks, Ben. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message