Ok, I've figured out that killing gnome-settings-daemon restores my settings in ~/.gtkrc-2.0. All I can say is, holy crap is this bad design! My configuration varies depending on whether some daemon happens to be running?! The daemon asserts its defaults ahead of the settings I've explicitly typed into my ~/.gtkrc-2.0?!
gnome-settings-daemon seems to have been started by some other program I ran. Is there some way of ensuring that it never gets started, or of asking it to defer to my ~/.gtkrc-2.0? BTW, README.Debian should be updated, because now even gnome-keybinding-properties doesn't permit setting Emacs bindings. Not to mention that as soon as I run it, it undoes the key mappings I have set with xmodmap. Message to GNOME people: Please give some consideration in your designs to leaving things alone when you have not been asked to get involved. Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
