Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!convex!cs.utexas.edu!usc!howland.reston.ans.net!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: 26 Jul 1993 09:09:25 -0500
Organization: Introl Corp.
Lines: 27
Message-ID: <230oil$os1@introl.introl.com>
References: <22h1vs$6a6@aggedor.rmit.OZ.AU> <22lm8l$c0k@cleese.apana.org.au> <22uoji$h3d@introl.introl.com> <1993Jul26.033520.19423@ucc.su.oz.au>
NNTP-Posting-Host: introl.introl.com
Keywords: netbsd, 386bsd, hack, capslock
In article <1993Jul26.033520.19423@ucc.su.oz.au> dawes@physics.su.OZ.AU (David Dawes) writes:
>
>Are you sure you are doing the remapping correctly? I've never had any
>problems swapping ctrl and caps-lock with XFree86. If you follow the
>example in the xmodmap(1) man page it should work fine. If you don't do
>it correctly you can see the behaviour you describe.
Wow, you're right. Actually, I wasn't forgetting to undefine the old definition.
I have been using the .Xmodmap file containing:
remove lock = Caps_Lock
add control = Caps_Lock
to turn my caps-lock key into a control key. This file works for every X
server I've tried except for the XFree86 server. The magic seems to be
that the XFree86 server applies the locking behavior to whetever key
has the "Caps_Lock" keysym. Now that I realize this, I still think it
is bogus behavior of the server to think that whatever key has the "Caps_Lock"
keysym should lock. Instead, it seems that it ought to lock whatever
key is used to achieve the "lock" modifier (at least that's the way that
the stock MIT server on Suns and all Visual and NCD X servers work).
- Tim
--
Tim Chase Introl Corp. Milwaukee, WI USA
Email: tim@introl.com Phone: +1 (414) 327-7171