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 168542 - Emacs key bindings overridden by gedit bindings
Emacs key bindings overridden by gedit bindings
Status: RESOLVED DUPLICATE of bug 150059
Product: gedit
Classification: Applications
Component: general
2.8.x
Other All
: Normal normal
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2005-02-25 20:38 UTC by Carmine F. Greco
Modified: 2005-02-26 09:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Carmine F. Greco 2005-02-25 20:38:07 UTC
Please describe the problem:
I set up GNOME to use Emacs-style key bindings.  I changed
/desktop/gnome/interface/gtk-key-theme to be "Emacs" and I added a line to
~/.gtkrc-2.0 that has 'gtk-key-theme-name = "Emacs"'  The key bindings work fine
in other GNOME applications, but gedit overrides most of the cursor movement
bindings with MS-style key bindings.

Steps to reproduce:
1. set /desktop/gnome/interface/gtk-key-theme to be "Emacs" in gconf-editor and
'gtk-key-theme-name = "Emacs"' in ~/.gtkrc-2.0

2. Edit a document in gedit

3. Try Ctrl-a, Ctrl-n, Ctrl-p, Ctrl-f


Actual results:
Ctrl-a selects all text, Ctrl-n opens a new window, Ctrl-p opens the print
dialog, and Ctrl-f opens the search dialog.

Expected results:
Ctrl-a should move the cursor to the beginning of the current line.
Ctrl-n should move the cursor to the next line.
Ctrl-p should move the cursor to the previous line.
Ctrl-f should move the cursor forward one character.

Does this happen every time?
Yes

Other information:
It seems like any Emacs key binding that is not already bound to an action be
gedit works just fine.  Ctrl-e for end of line, Ctrl-d for delete character,
Ctrl-k for delete to end of line, and Ctrl-y for paste all work.
Comment 1 Paolo Borelli 2005-02-26 09:08:09 UTC

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