Bug#309530: mozilla-firefox: emacs key shortcuts not recognized

[Andrew Pimlott]

On Fri, May 20, 2005 at 09:34:36PM +0200, Loïc Minier wrote:
>  When you reassigned this bug to Gtk, I thought I had seen a web page
>  explaining all of this, but I couldn't get my hand on it again.  Guess
>  what?  I've found it:
>     <http://kb.mozillazine.org/Emacs_Keybindings_(Firefox)>

Thanks, I think I saw that at one point too.

>  This ain't Firefox specific, and it will tell that there are two
>  layers: the Gtk configuration, and the GNOME configuration of Gtk, the
>  second being edited via gconf.

This isn't very useful if one is used some of the time, and the other is
used other times, and the difference is something that is invisible to
the user (whether gnome-session-daemon is running).  Really, this is a
terrible user experience.  Besides, the gtkrc-2.0 settings have been
documented for some time, and since they are explicitly entered, they
should override any default gnome-sesson-daemon settings.

>  Could you please follow the suggestion on the page I pointed you to and
>  report whether that helped?

I make a quick test, and changing the setting with gconf-editor (as
described on that page) it does fix the keybindings.  However,
gnome-settings-daemon still breaks my keyboard configuration when it
starts, because it (seemingly) reasserts my XKB settings, overwriting
the changes I added with xmodmap.  I can see no way to turn this off.

So the real "solution" for me is preventing gnome-settings-daemon from
running.

>  If it did, I would be glad to complement the README.Debian of
>  libgtk2.0-0 and eventually will suggest Gtk 2 apps getting report of
>  the problem to link to this file.

Yes, that would be good.

> > Message to GNOME people:  Please give some consideration in your designs
> > to leaving things alone when you have not been asked to get involved.
> 
>  PS: Your rant doesn't reach GNOME people and is useless in this form.
>  I must add that Gtk and GNOME people are quite close-working, so your
>  reproach isn't well-targetted.

Well, since this bug is now on Gtk, I thought it might be a good
channel.  But maybe I'll paste some of this text into a GNOME bug report
(where it can get ignored because it doesn't affect GNOME-centric
users).

Andrew