Skip to main content

Killing the CAPS LOCK key

For some time, I have been interested in disabling the CAPS LOCK key. I frequently press it accidentally and it is a continuing aggravation. The old way of doing it no longer worked and I got discouraged.

This might work. (Skip to the very last Update below for a workable solution for me.)

Find the file in /etc/X11/xorg/conf.d that contains the "InputClass" section. Into that section, add

Option "XkbOptions" "caps:none"
Option "XkbOptions" "shift:both_capslock"

At the command line:

$ setxkbmap -option "caps:none"

$ setxkbmap -option "shift:both_capslock"

But that will not survive a reboot; the file edit above will or you can add it to rc.local.

Update: I have been unsuccessful using this in rc.local, so I created an entry in ~/.config/autostart that had both commands after EXEC= and that failed. It was not until I created two .desktop files, k1 and k2, that executed the commands in the proper order that didn't always work so well.

Update: I have not had a consistent experience using rc.local or the .desktop files in this manner, but since I use the LXDE desktop, I have some better options.

FINALLY, . . .
I use the LXDE desktop and this solution only applies to that. It may work in a similar fashion for other desktops. You just need to locate a file or location of a file that will be executed every time th desktop environment is launched.

In /etc/lxdm there are several files that provide the opportunity to set options system wide. In the PostLogin file, I added the following two lines:

setxkbmap -option "caps:none"
setxkbmap -option "shift:both_capslock"

Now, capslock is disabled every time I log in. The information was found in the well-maintained ArchLinux Wiki.

FINAL UPDATE SUCCESS!!
I stumbled upon the file /etc/default/keyboard. Inside, it reads

 # KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL=pc105
XKBLAYOUT=us
XKBVARIANT=
XKBOPTIONS=
BACKSPACE=guess

Consulting the man page for keyboard reveals the following interesting information

KEYBOARD(5)             
Console-setup User's Manual    

NAME
       keyboard - keyboard configuration file

DESCRIPTION
       The  keyboard file describes the properties of the keyboard. It is read by setupcon(1) in order to configure the keyboard on the  console.   In Debian  systems  the  default  keyboard layout is described in /etc/default/keyboard and it is shared between X and the console.
       The specification of the keyboard layout in the keyboard file is  based on the XKB options XkbModel, XkbLayout, XkbVariant and XkbOptions.  Unfortunately, there is little documentation how to use  them.   Description  of all possible values for these options can be found in the file xorg.lst.
       You might want to read “The XKB Configuration Guide” by Kamil Toman and Ivan U. Pascal:
http://www.xfree86.org/current/XKB-Config.html

       Other possible readings are:
      https://wiki.archlinux.org/index.php/X_KeyBoard_extension
http://pascal.tsu.ru/en/xkb/
http://www.charvolant.org/~doug/xkb/

The complete XKB-specification can be found on
http://xfree86.org/current/XKBproto.pdf

       The file keyboard consists of variable settings in POSIX format:

              VARIABLE=VALUE
Only  one assignment is allowed per line.  Comments (starting with '#') are also allowed.

A descriptions of options, other errata and some examples follow that.

Of interest to use are those associated with XKBOPTIONS and examples of that are given are


EXAMPLES
       The following configuration will give you the standard US QWERTY layout us). The  key will act as a compose key (compose:menu) and will act as third control key (ctrl:nocaps).

           XKBLAYOUT=us
           XKBVARIANT=
           XKBOPTIONS=compose:menu,ctrl:nocaps

       In the following configuration the right   key  (grp:toggle)  will toggle between US QWERTY layout (us) and Greek (gr) layout.  The option grp_led:scroll is ignored on the console but in X in means to  use  the     ScrollLock  keyboard  led  as  indicator  for the current layout (US or Greek).

           XKBLAYOUT=us,gr
           XKBVARIANT=
           XKBOPTIONS=grp:toggle,grp_led:scroll

       In the following configuration the  +  key  combination will  toggle grp:ctrl_shift_toggle) between French keyboard (fr) without dead keys (nodeadkeys) and British (gb) “Dvorak” (dvorak) keyboard.
       The  right key will be a compose-key (compose:rwin) and the right  key will function as AltGr (lv3:lalt_switch).

           XKBLAYOUT=fr,gb
           XKBVARIANT=nodeadkeys,dvorak
           XKBOPTIONS=grp:ctrl_shift_toggle,compose:rwin,lv3:ralt_switch

My goal is to disable the CAPSLOCK key and turn the left Windows key into a RETURN key.

So, perusing xorg.lst we find

caps:none            Caps Lock is disabled
lv3:enter_switch     Enter on keypad

Therefore, in /etc/default/keyboard we enter

XKBOPTIONS=caps:none,lwin:enter_switch

. . . and reboot.


RESOURCES 

 https://www.linux.com/learn/hacking-your-linux-keyboard-xkb

ArchLinux Wiki - LXDE

xorg.lst
Labels:

Comments

Post a Comment

Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

DOS4GW.EXE The Tenberry DOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox , so they can be played on Linux. However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a. It's not free at US$49, but you can downloaded it here . Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5. Open Souce to the Rescue There are better performing, free and Open Source alternatives available and worth a look. DPMI Explained Let's unders
1 comment
Read more

Return to Castle Wolfenstein for Modern Linux

Return to Castle Wolfenstein is a first-person shooter originally released on November 19, 2001. The game, like many other classic games, is available at GOG.com and costs only US$5.99. iortcw for Linux Don't bother with old and crusty Linux binaries offered by idsoft; they are problematic and it's painful to use them on a modern Linux. Fortunately for us, there are more modern GPL-licensed Linux binaries available for 32- and 64-bit systems as well as high resolution textures packages. The project at GitHub provides source code that can also be compiled for MS Windows using MinGW. iortcw for Windows and Mac You can download pre-compiled binaries for 32- and 64-bit Linux, MS Windows and Mac from here . Let's put our files in /usr/local/games/rtcw . As root, extract the downloaded .ZIP file for your architecture to  /usr/local/games/rtcw . All we are missing are the game data files. I purchased them from GOG.com. The game installer downloaded from GOG.com can be
1 comment
Read more

Unreal Tournament GOTY/UT99 for Modern Linux

Released on November 16, 1999, Unreal Tournament (also known as UT99) is an arena first-person shooter for Multiplayer on-line competition or you can play against bots off-line. It features several game types, with more details provided at Wikipedia . The game was re-released on February 25, 2000 as Unreal Tournament Game of the Year Edition (GOTY) which included the three bonus packs released previously and additional mods, or game modifiers that had become popular. It is the GOTY version that is available from STEAM or  GOG.com . The GOG version for Windows installs in Linux and plays well using WINE , PlayOnLinux or Codeweaver's Crossover . There is a Linux binary available in two versions, one for the original game and one for the GOTY edition . Also provided at that site is the Official Bonus Pack with a Linux installer. All these Linux installers are created with makeself . There are some issues using such a crusty old Linux binary. Let's see why getting a Lin
2 comments
Read more