Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!news.introl.com!not-for-mail From: tim@introl.com (Tim Chase) Newsgroups: comp.os.386bsd.bugs Subject: Re: [HACK:] fix CAPSLOCK for good... Date: 25 Jul 1993 14:57:38 -0500 Organization: Introl Corp. Lines: 26 Message-ID: <22uoji$h3d@introl.introl.com> References: <22h1vs$6a6@aggedor.rmit.OZ.AU> <22lm8l$c0k@cleese.apana.org.au> NNTP-Posting-Host: introl.introl.com Keywords: netbsd, 386bsd, hack, capslock Cc: In article <22lm8l$c0k@cleese.apana.org.au> newton@cleese.apana.org.au (Mark Newton) writes: >In article <22h1vs$6a6@aggedor.rmit.OZ.AU> zak@rmit.edu.au writes: > ... >Of course, those of us who run X-windows would know that you can >use xmodmap to achieve exactly the same result without having to >patch the kernel. :-) Unfortunately, if you're using a stock XFree86 server, mapping the caps-lock key to a different modifier results in a different modifier that _still has the locking behavior_. I forgot the file that needs hacking, but I always rip the code out of the XFree86 server that causes this to happen. Since remapping the caps-lock key "does the right thing" (i.e. doesn't produce a key with a locking behavior) on other host systems (i.e. Sun, etc.) using a MIT based server, I can only presume that the XFree86 server needs modification to detect the caps-lock key being remapped and to disable the locking behavior. -- Tim Chase Introl Corp. Milwaukee, WI USA Email: tim@introl.com Phone: +1 (414) 327-7171