After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 317801 - Keyboard Shortcuts doesn't include Text Editing Shortcuts
Keyboard Shortcuts doesn't include Text Editing Shortcuts
Status: RESOLVED DUPLICATE of bug 329073
Product: gnome-user-docs
Classification: Core
Component: user-guide
2.4
Other Linux
: Normal normal
: ---
Assigned To: Thijs Thiessens
Thijs Thiessens
Depends on:
Blocks:
 
 
Reported: 2005-10-03 07:57 UTC by Sebastien Bacher
Modified: 2006-04-10 07:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Sebastien Bacher 2005-10-03 07:57:56 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=16876

"In Breezy Colony 5 [-and- in Hoary, btw...]

I'm trying to change my text editing shortcuts to Emacs.  If I go to System ->
Preferences -> Keyboard Shortcuts and then collapse all categories, I'm only
left with 3:  Desktop, Sound, and Window Management.  Yet if I click on Help
there, the frame that pops up quite clearly has a table mentioning the
nonexistent Text Editing Shortcuts.  I don't know if this is a documentation bug
or a program bug (or both), but it's persisted at least since Hoary.  Some
searching has also revealed other people in other distributions complaining
about this being missing.

What's more, I'm unsure how I'm actually supposed to do this even without the
GUI.  Searching the web has revealed setting gtk-key-theme-name in ~/.gtkrc-2.0
(which presumably would be seen by Gnome 2.x), but I also see conflicting pages
claiming that this is deprecated (and, in fact, ignored!) and that one should
now be using the "gnome-keybindings-properties" dialog in gconf-editors. 
However, I can't see a way to launch gconf-editors from any toolbar, and
expecting any non-expert user to know about this program and launch it from the
command line seems like we're expecting them to do lots of websearching first to
even find it (since the UI doesn't make it available).

So what's the -right- way for me to do this, and what's going on with the
(apparently long-standing) inconsistency between the Keyboard Shortcuts dialog
and its self-documentation?"
Comment 1 Joachim Noreiko 2006-02-08 16:37:38 UTC
The documentation being out of date is covered by Bug 329073.
Would you like me to close this bug as a duplicate, or move it to Keyboard Shortcuts application?
Comment 2 Daniel Holbach 2006-04-10 07:48:50 UTC

*** This bug has been marked as a duplicate of 329073 ***