| |||||||||||||
GoodGoodPosted Aug 5, 2010 8:45 UTC (Thu) by jschrod (subscriber, #1646)In reply to: Good by ncm Parent article: GUADEC: A message from the release team
Why do you want to take Emacs key bindings away from us Emacs-using folks? What is your goal in alienating us?
On the one hand, you speak up against fewer choices (Nautilus) because you don't like it and it irks you.
On the other hand, you speak up for fewer choices (Emacs key bindings) because you don't care and have no use for it.
Very selfish, don't you think?
So, should I do like you, and speak up for forcing Nautilus on you and demanding Emacs key bindings for me, because I don't care about Nautilus, but care about Emacs key bindings? No, I won't do the same as you -- I'm for _your_ ability to not use Nautilus *and* _my_ ability to use Emacs keys. (And I don't need an UI to configure it, btw; gconftool is fine for me.)
(Log in to post comments)
Good Posted Aug 5, 2010 9:33 UTC (Thu) by ncm (subscriber, #165) [Link]
Such confusion. I use Emacs key bindings myself, but I suppose Gnome 3 will eliminate them, and then I'll have to do without or switch to KDE.
By the way, for those who haven't discovered it yet, the way to add Emacs key bindings to Gnome programs that haven't eliminated the option yet is to go in Gconf to /desktop/gnome/interface/gtk_key_theme and type "Emacs" into the text box.
I don't understand why they're not on by default, in addition to Home/End/etc. buttons. Would it be so bad if somebody accidentally hit ctrl-A and their cursor moved?
Good Posted Aug 5, 2010 9:46 UTC (Thu) by jschrod (subscriber, #1646) [Link]
Sorry, I really understood you as being for Emacs key binding removal. My apologies.
I blame it on not being a native English speaker. ;-)
Good Posted Aug 5, 2010 9:50 UTC (Thu) by bronson (subscriber, #4806) [Link]
Yes. Ctrl-A on pretty much every platform means Select All.
Good Posted Aug 5, 2010 11:45 UTC (Thu) by nix (subscriber, #2304) [Link]
And Select All is such a *useful* feature in an input line.
Good Posted Aug 6, 2010 19:21 UTC (Fri) by spitzak (guest, #4593) [Link]
This is trivially fixed by making ^A select all if you are already at the start of a line, so typing it twice works.
Good Posted Aug 10, 2010 9:25 UTC (Tue) by dgm (subscriber, #49227) [Link]
Why not do it the other way? Hit ^A once and you select all text, hit it twice and the cursor is moved to the beginning of the line. For extra fun, hit it again to remove the selection. More hits could bring other functionality too, or you can make it a cycle that starts over again.
Note to GNOME/GTK+ hackers: this post was supposed to be completely facetious, not a real suggestion. Please DO NOT DO THAT.
Good Posted Aug 10, 2010 15:32 UTC (Tue) by spitzak (guest, #4593) [Link]
I suspect that you are just making a joke about my suggestion, but what you suggest would require remembering the cursor position while select-all is done, which most editors do not do (the cursor is one end of the selection). Also cyclic modes are a very bad idea, though they were popular with some older Unix editors, they are not user-friendly as the user has to watch to get them to stop, rather than just blindly hitting the key many times to get at the state they want (if it is the last state).
Good Posted Aug 11, 2010 23:49 UTC (Wed) by nix (subscriber, #2304) [Link] Sounds like you want the immortal gnxt.
Good Posted Aug 13, 2010 12:34 UTC (Fri) by richdawe (subscriber, #33805) [Link]
That would be fun for people using screen's default key bindings, where Ctrl+A starts screen's special key sequences.
I've just about managed to reprogram my fingers to type Ctrl+A A to go to the start of the line instead of just Ctrl+A (in screen sessions).
|
|||||||||||||