Skip to main content
6 events
when toggle format what by license comment
Apr 13, 2017 at 12:37 history edited CommunityBot
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Nov 13, 2011 at 4:25 vote accept Alf P. Steinbach
Nov 12, 2011 at 23:48 comment added Alf P. Steinbach Well, it still works after renaming that file and rebooting. And the terminal still remembers old command history after reboot. With silly persistent dynamic states like that, I think it must be rather difficult to hunt down bugs: they can't be reliably reproduced in such an interfering environment. I think further evidence of that is how the bug about AltGr has gone yoyo: closed as resolved, re-opened, closed as resolved, re-opened, so on and on. So I think it would be a Good Idea(TM) to severely punish the person who introduced that persistence of settings & state. :-)
Nov 12, 2011 at 23:34 comment added Gilles 'SO- stop being evil' @AlfP.Steinbach The keycode is determined by your hardware (or hardware emulator, in a VM) and by your kernel and X server version. On PC keyboards, the right Alt key has keycode 113 on older Linux distributions and 108 on newer ones (my example with 66 is because I have AltGr on the Caps Lock key). I asked a while ago how to automatically determine whether I have an “old” or “new” system regarding keycode assignments.
Nov 12, 2011 at 23:31 comment added Alf P. Steinbach It is an interesting answer, using keycode 66. In my comment before you posted this answer, I noted that keycode 113, which I just copied and pasted from the net, works for that line. Now when I run xevas you suggest, it reports keycode 108. Yet the line I copied from the net works. So it apparently has nothing to do with the keycode. I changed it to 66, just for fun, and rebooted: it still works. So I conclude it's not something technically accurate at all, but evidently a Heisenbug in Ubuntu.
Nov 12, 2011 at 20:23 history answered Gilles 'SO- stop being evil' CC BY-SA 3.0