Date: Wed, 8 Mar 2000 21:16:53 +0000 From: Mark Ovens <mark@ukug.uk.freebsd.org> To: Jim Weeks <jim@siteplus.com> Cc: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@freebsd.org> Subject: Re: weird vi behavior in X Message-ID: <20000308211653.B234@parish> In-Reply-To: <38C6836D.112501B1@siteplus.com>; from jim@siteplus.com on Wed, Mar 08, 2000 at 11:44:30AM -0500 References: <38C681B9.46E48541@siteplus.com> <38C6836D.112501B1@siteplus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 08, 2000 at 11:44:30AM -0500, Jim Weeks wrote:
> I meant to say I have NOT been able to stop this behavior.
>
> Jim Weeks wrote:
>
> > Good day,
> >
> > I am running the latest version of STABLE and Afterstep. In fact I did
> > a make world this morning. Any way, when searching in vi from an xterm
> > if I do "/search" and hit the enter button on the numeric key pad vi
> > goes to the line above the match and inserts an "M". I have tried
> > several keymaps and several adjustments to XF86Config and have been able
> > to stop this behavior. It doesn't happen if you use the normal enter
> > key. Just the one on the numeric keypad.
> >
> > Any one else seen this?
Yeah, and you will also find that the cursor keys on the numeric
keypad will do similar things. The output from xev(1) gives us a clue:
The "normal" RETURN key:
KeyPress event, serial 21, synthetic NO, window 0x4c00001,
root 0x25, subw 0x0, time 3362131098, (97,79), root:(170,237),
state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
" XLookupString gives 1 characters: "
KeyRelease event, serial 21, synthetic NO, window 0x4c00001,
root 0x25, subw 0x0, time 3362131157, (97,79), root:(170,237),
state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
" XLookupString gives 1 characters: "
...and the numeric keypad one:
KeyPress event, serial 21, synthetic NO, window 0x4c00001,
root 0x25, subw 0x0, time 3362128432, (97,79), root:(170,237),
state 0x10, keycode 108 (keysym 0xff8d, KP_Enter), same_screen YES,
" XLookupString gives 1 characters: "
KeyRelease event, serial 21, synthetic NO, window 0x4c00001,
root 0x25, subw 0x0, time 3362128492, (97,79), root:(170,237),
state 0x10, keycode 108 (keysym 0xff8d, KP_Enter), same_screen YES,
" XLookupString gives 1 characters: "
They produce different keysyms, Return and KP_Enter. You can use
xmodmap(1) to fix it.
HTH
> >
> > Thanks,
> >
> > Jim
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
--
Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
BSD: Are you guys coming, or what?
-Poster at LinuxWorld 2000
________________________________________________________________
FreeBSD - The Power To Serve http://www.freebsd.org
My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org http://www.radan.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000308211653.B234>