< ^ txtMon Mar 23 10:18:17 EDT 2015 I went to bed at a reasonable hour, slept OK, and woke up on time. Still... I moving pretty slowly this morning. Goals: Work: - Work on GRUB notes Done. - Review invoices Done. Home: - Work on S&W Complete re-typeset Done. I like to remap my Caps Lock key to send Control. Some time ago, I started using `setxkbmap -option ctrl:nocaps` in my .xsession to do it, since xmodmap is apparently deprecated. Unfortunately, this new method is not as reliable as xmodmap. Since I started using `setxkbmap`, I have noticed that whatever changes I make with it occasionally get revered to defaults. Lately, on my work machine, this has been happening with annoying frequency. I may have figured out part of the problem. Looking at `/var/log/messages`, I noticed the log shows my keyboard getting "disconnected" and immediately found as a new device. To test, I actually unplugged the keyboard; after plugging it back in, my setxkbmap settings were undone. So: 1) phantom USB disconnects are bullshit 2) regardless of the above, I should be able to unplug/plug my keyboard without loosing my keymap A little googling tells me I'm not alone. This, or issues very like this, have been around for years. (https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/287215) http://x.debian.net/howto/configure-input.html `man keyboard` I edited '/etc/defaults/keyboard' to include: XKBOPTIONS="ctrl:nocaps" and then ran: $ sudo udevadm trigger --subsystem-match=input --action=change I tested by unplugging/plugging my keyboard, and option appears to have stuck. Good. I'd still be happier if there was a reliable way to set keyboard options in per-user dotfiles, rather than as a system-wide default.
< ^ txt