GNOME and the way forward
Posted Aug 18, 2005 4:55 UTC (Thu) by iabervon
In reply to: GNOME and the way forward
Parent article: GNOME and the way forward
The problem with the Gtk emacs keybindings is that Gtk implements them differently from how emacs does. Consider, for example, Ctrl-K.
I use it as the sole way I copy or move text in Emacs, by hitting it repeatedly until the area I want to copy has been cut and then hitting Ctrl-Y if I wanted to keep it, moving to the destination, and hitting Ctrl-Y. In Gtk, however, Ctrl-K has no effect, unless I've told it that I want emacs keybindings, in which case it deletes all of the text I want to copy. Alternatively, I could try using Ctrl-W, but that tends to close the window instead (definitely if the text entry doesn't have focus). After I've forgotten that I'm using Gtk and done something wrong, I type Ctrl-_ to undo it, but this has no effect. I don't know if a set of keybindings could be designed to be more hostile to emacs users. (That page tells you not to use the standard application shortcut keys for anything else, and then uses one of them in the emacs keybinds for something else; it also tells applications not to use symbols that require shift in shortcuts, and then doesn't bother to implement one of the emacs shortcuts that is therefore free.) In order to save myself, I avoid using any shortcuts or pressing Ctrl or Alt while a Gtk application has focus, and never restructure my text.
I will note that OS X's emacs keybindings actually get Ctrl-K right, so it is possible. (Pressing Ctrl-K cuts to the end of the line, unless the cursor is at the end of the line, in which case it cuts the line break, and pressing it again without intervening keypresses appends the removed text to the clipboard rather than replacing it.)
to post comments)