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 259331 - emacs keybindings don't work in composer
emacs keybindings don't work in composer
Status: RESOLVED DUPLICATE of bug 269404
Product: GtkHtml
Classification: Other
Component: Editing
3.30.x
Other All
: Normal minor
: ---
Assigned To: gtkhtml-maintainers
gtkhtml-maintainers
evolution[composer], AP4
Depends on:
Blocks:
 
 
Reported: 2004-05-31 02:06 UTC by Michael Gratton
Modified: 2010-10-13 03:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Gratton 2004-05-31 02:06:28 UTC
After setting the key theme preference to Emacs-style (using the
gnome-keybinding-properties capplet), the compose message window continutes
to use what I assume is the default GTK/Gnome key theme instead of the
preferred one. Most (all?) other test fields in Evolution do honour the
preferred key theme correctly.

The problem is two-fold:

The header text boxes ("To", "Subject", etc) partly honour the preferred
key theme, but it seems the application overrides certain bindings in a
broken way. The most annoying one, Ctrl-a selects the entire contents of
the text box, rather than moving the cursor to the start of the text field.
This seems to be caused by the Edit > Select All menu item (which seems to
be of dubious utility in a text field).

The message body text area is more problematic (but is at least
self-consistent, unlike the text fields above :) because it does not seem
to honour the the preferred key theme at all. For example, Ctrl-k does not
kill the remainder of the line. Ctrl-e does not move to the end of the line.

These issues hurt the consistency of Evolution with not only itself, but
with the rest of the Gnome desktop. It makes writing at any length quite
painful.
Comment 1 Jeffrey Stedfast 2004-05-31 03:46:53 UTC
the subject is just a GtkEntry so if it's a problem with subject, then
it's a gtk bug.

To/Cc/Bcc are e-entry boxes I think (or did we convert to using
GtkEntry for them too?)
Comment 2 Radek Doulik 2004-06-09 16:13:41 UTC
the problem is probably 1/2 e-entry and 1/2 gtkhtml emacs keybindings.

for gtkhtml part look at http://bugzilla.gnome.org/show_bug.cgi?id=241187
Comment 3 Radek Doulik 2004-06-24 13:24:56 UTC
EEntry is pain to mantain, bacuse it's based on
gtktable/etext(gnomecanvas). We will base it on GtkEntry in 2.1 which
should solve it. Rescheduling.
Comment 4 Calum Benson 2006-04-26 16:53:14 UTC
Updating keywords, not really an "accessibility" issue IMHO.
Comment 5 Calum Benson 2006-04-26 17:07:48 UTC
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Comment 6 André Klapper 2006-06-25 14:37:30 UTC
removing old target milestone.
Comment 7 André Klapper 2009-11-08 16:11:36 UTC
This report has not seen any changes or updates for more than 3 years.

Also, GAL was merged into Evolution in June 2005. Actual GAL bugs are now located in the Product "Evolution", component "GAL". The external, separate GAL codebase will not receive any changes.

We kindly ask you to check whether the issue you have reported here still happens in GNOME 2.26 or 2.28. 
If so, please update this report by adding a short comment, removing the NEEDINFO state, updating the "Version" field and moving this to the Evolution product (if you have sufficient Bugzilla rights to do so).

Again thank you for reporting this bug and we are sorry it could not be handled for the version you originally used here.
Comment 8 Michael Gratton 2009-11-09 09:07:41 UTC
This is still a problem in Evo 2.28.1. Adjusting bug fields accordingly.

To reproduce:

 - set gconf key /desktop/gnome/interface/gtk_key_theme to "Emacs"
 - check the standard Emacs keybindings work in normal GTK text fields
 - create a new mail message in Evolution
 - try to use Emacs key bindings in the address/subject/body text fields

An example key binding to try is Ctrl-k, which deletes all text after the cursor until the end of the line.
Comment 9 Michael Gratton 2009-11-09 09:09:27 UTC
PS: I can't seem to remove NEEDINFO. Can someone do that? Thanks.
Comment 10 André Klapper 2009-11-09 09:51:53 UTC
Thanks for updating!
Comment 11 Matthew Barnes 2010-10-13 03:21:09 UTC

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