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 108094 - epiphany doesn't respect emacs text editing shortcuts
epiphany doesn't respect emacs text editing shortcuts
Status: RESOLVED NOTABUG
Product: epiphany
Classification: Core
Component: Interface
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Marco Pesenti Gritti
Marco Pesenti Gritti
: 134061 139449 143490 365499 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-03-11 14:49 UTC by hugo hallqvist
Modified: 2006-10-27 10:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description hugo hallqvist 2003-03-11 14:49:52 UTC
Epiphany version 0.5.0 doesn't seem to respect emacs text editing
shortcuts. I have chosen Emacs shortcuts in keyboard shortcuts, and most
other gnome-programs follow it, however epiphany doesn't. Entering Ctrl+D
opens up bookmark add dialog instead of deleting a character, Ctrl+A marks
all of text in a text-box instead of going to beginning of line and so on.
Comment 1 Dave Bordoley [Not Reading Bug Mail] 2003-03-11 17:34:30 UTC
Could this be a mozilla bug?
Comment 2 Marco Pesenti Gritti 2003-03-11 18:16:30 UTC
Not mozilla I think.
Does these other app have key bindings (in the menus) that conflicts
with emacs bindings ?
I think in gtk keys are handled first by menus ... so I think this
should be considered a gtk issue. We cant really change our
accellerators to not conflict with emacs.
Comment 3 Calum Benson 2003-08-07 16:08:16 UTC
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)
Comment 4 Andres Salomon 2003-08-14 18:35:16 UTC
Galeon 2 doesn't appear to have ctrl shortcuts that conflict w/ emacs
keybindings.  mozilla and firebird, otoh, do things differently
depending upon where focus is; if focused on the url bar, or any text
entry widget (ie, html text input forms on a rendered page), it does
what an emacs keybinding should.  If focused anywhere else on the
application, it does whatever keyboard shortcut is registered.  For
ctrl-u, the emac keybinding is to clear the line, and the shortcut is
to view source.
Comment 5 Marco Pesenti Gritti 2003-08-14 18:38:33 UTC
Closing as NOTABUG because I think it's intentional gtk behavior.
Someone should bring the issue on gnome mailing lists though.
Comment 6 Andres Salomon 2003-08-17 00:23:28 UTC
This really should not be resolved; at best, WONTFIX.  It's certainly
a bug, as _every_ other gtk/gnome app handles this correctly except
for epiphany.
Comment 7 Marco Pesenti Gritti 2003-08-17 07:57:23 UTC
Can you give examples of gtk2 apps (not mozilla which doesnt actually
use gtk menus) which beahve like you would like ?
I tried with evolution ctrl+d and it use the menu, not the emacs key.
Comment 8 Lars Weber 2004-01-24 15:17:29 UTC
I think this is not only a problem with menu-shortcuts taking
precedence over editing-shortcuts but more generally a problem of the
non-standard editing behaviour of on-page text entries (at least with
the Emacs shortcuts selected, not sure if it's also true with the
default shortcuts.)

Some examples of differences between the editing-behaviour of on-page
entries and of Gtk entries (the difference even exists between
"normal" Epiphany entries like the location bar and on-page entries):

- When navigating the cursor or the selection by word (i.e. using
Ctrl-Left and Ctrl-Right) on-page entries consider every sequence of
non-white-space characters to be words; Gtk-entries OTOH only consider
sequences of letters or numerals to be words.

- When navigating by word, with on-page entries the cursor or
selection also stops twice for each word (i.e. at the beginning and
the end of it) whereas it only stops once with Gtk-entries.

- When "killing" lines from the cursor to the end of the line (i.e.
using Ctrl-k), with on-page entries the line is killed only to the end
of the line as it is currently shown in the entry, whereas in
Gtk-entries the shortcut always kills to the real end of the line
(i.e. ignoring automatic line breaks).

These are the only differences that I remember right now, but I think
I could come up with a few more given a little more time.

Anyway, I don't know how difficult it would be to make on-page
text-entries behave exactly like their normal Gtk counterparts ... but
if it could be done that would be pretty cool because I quite
reqularly notice the difference in behaviour as a minor annoyance.
Comment 9 Christian Persch 2004-02-10 23:59:31 UTC
*** Bug 134061 has been marked as a duplicate of this bug. ***
Comment 10 Christian Persch 2004-04-08 09:21:26 UTC
*** Bug 139449 has been marked as a duplicate of this bug. ***
Comment 11 Marco Pesenti Gritti 2004-04-17 08:28:16 UTC
*** Bug 139449 has been marked as a duplicate of this bug. ***
Comment 12 Sean Proctor 2004-04-17 15:10:46 UTC
I think there are two quite different bugs here, and I think one of them is
quite fixable. The menu bit, you can use g_signal_connect_after to let the
regular bindings take precedence AFAIK.
Comment 13 Christian Persch 2004-06-01 10:58:33 UTC
*** Bug 143490 has been marked as a duplicate of this bug. ***
Comment 14 Christian Persch 2006-10-27 09:27:58 UTC
*** Bug 365499 has been marked as a duplicate of this bug. ***
Comment 15 Wouter Bolsterlee (uws) 2006-10-27 10:57:23 UTC
copy/paste from #365499:

I think that in the gconf emacs keybindings setting, Control+N and Control+P
should be linked to DOWN and UP keys respectively.

This is primarily in response to users of the epiphany browser, complaining
that they can't navigate dropdown boxes via the home keys.