Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!cornell!uw-beaver!newsfeed.rice.edu!rice!news.Rice.edu!rich From: rich@Rice.edu (Richard Murphey) Subject: Re: ServerNumLock and XFree386 In-Reply-To: kuku@acds.physik.rwth-aachen.de's message of 3 Dec 1992 22:13:23 GMT Message-ID: <RICH.92Dec3221718@omicron.Rice.edu> Sender: news@rice.edu (News) Reply-To: Rich@rice.edu Organization: Department of Electrical and Computer Engineering, Rice University References: <1fm0q3INN3aj@urmel.informatik.rwth-aachen.de> Date: Fri, 4 Dec 1992 04:17:18 GMT Lines: 30 In article <1fm0q3INN3aj@urmel.informatik.rwth-aachen.de> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: Excuse me if this is not too close bsd related but X386 instead but as I saw many X386 heads hanging around here ... I wanted to map some keypad (vt100 sequences) to NumLock and the other keys in the key pad of the PC board of my 386BSD PC. I tried with xev that every key hit gives an event. But when I map XTerm.VT100.Translations: #override \ <Key>NumLock: string("something")\n\ the action takes place only every second time. This is independent of whether I have ServerNumLock enabled or disabled in my Xconfig file. Is this a bug or a feature or is it simply my misunderstanding of the NumLock key meaning. I thought the special behaviour could be switched off by ServerNumLock. NumLock is a modifier key, like caps lock, and that's why it acts this way. You can use xmodmap to reassign that key code to some other key sym that has normal behavior and then use the tranlations above. Rich -- --Chris Christoph P. U. Kukulies kuku@acds.physik.rwth-aachen.de *** Error code 1 Stop.