From: David Kastrup <dak@gnu.org>
To: rms@gnu.org
Cc: Mike Mattie <codermattie@gmail.com>, ams@gnu.org, emacs-devel@gnu.org
Subject: Re: Why Emacs needs a modern bug tracker
Date: Sun, 06 Jan 2008 19:18:28 +0100 [thread overview]
Message-ID: <85abnihl6z.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1JBZvy-0001nv-2d@fencepost.gnu.org> (Richard Stallman's message of "Sun, 06 Jan 2008 13:09:18 -0500")
Richard Stallman <rms@gnu.org> writes:
> I highly recommend firemacs. It's a firefox add-on that rebinds most
> of the editing keys to Emacs defaults.
>
> https://addons.mozilla.org/en-US/firefox/addon/4141
>
> I've been wanting that for ages.
Place the line
gtk-key-theme-name = "Emacs"
into the file ~/.gtkrc-2.0 and that's basically it. For all GTK+
applications, not just firefox.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-01-06 18:18 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 16:44 Why Emacs needs a modern bug tracker Eric S. Raymond
2008-01-04 17:33 ` Andreas Röhler
2008-01-04 18:29 ` Eric S. Raymond
2008-01-04 18:38 ` Gianluca Della Vedova
2008-01-05 14:31 ` Richard Stallman
2008-01-05 18:50 ` Gianluca Della Vedova
2008-01-05 19:51 ` Drew Adams
2008-01-05 19:58 ` Óscar Fuentes
2008-01-05 20:13 ` Sven Joachim
2008-01-05 20:28 ` Drew Adams
2008-01-06 10:47 ` Richard Stallman
2008-01-05 22:39 ` Óscar Fuentes
2008-01-06 18:09 ` Richard Stallman
2008-01-06 19:57 ` Óscar Fuentes
2008-01-06 22:29 ` Óscar Fuentes
2008-01-07 11:31 ` Richard Stallman
2008-01-04 19:20 ` Óscar Fuentes
2008-01-04 19:40 ` Drew Adams
2008-01-04 23:25 ` Alan Mackenzie
2008-01-05 0:44 ` Óscar Fuentes
2008-01-05 1:23 ` Miles Bader
2008-01-05 2:54 ` Óscar Fuentes
2008-01-05 15:38 ` Eli Zaretskii
2008-01-05 16:33 ` Juanma Barranquero
2008-01-05 19:05 ` Óscar Fuentes
2008-01-05 19:12 ` Lennart Borgman (gmail)
2008-01-05 20:00 ` Eli Zaretskii
2008-01-05 20:38 ` Óscar Fuentes
2008-01-05 21:55 ` Reiner Steib
2008-01-05 22:05 ` David Kastrup
2008-01-05 22:48 ` Óscar Fuentes
2008-01-05 23:25 ` Eli Zaretskii
2008-01-05 22:00 ` Bastien
2008-01-05 22:21 ` Óscar Fuentes
2008-01-05 23:32 ` Bastien
2008-01-06 0:52 ` Bastien
2008-01-07 17:15 ` Richard Stallman
2008-01-08 1:06 ` Bastien
2008-01-06 10:46 ` Richard Stallman
2008-01-08 23:49 ` Thien-Thi Nguyen
2008-01-09 1:13 ` Leo
2008-01-09 1:48 ` Thien-Thi Nguyen
2008-01-09 1:28 ` Andrea Russo
2008-01-09 1:49 ` Thien-Thi Nguyen
2008-01-05 12:23 ` Alan Mackenzie
2008-01-05 17:40 ` Alfred M. Szmidt
2008-01-06 1:10 ` Mike Mattie
2008-01-06 18:09 ` Richard Stallman
2008-01-06 18:18 ` David Kastrup [this message]
2008-01-06 21:27 ` Jan Djärv
2008-01-06 21:35 ` David Kastrup
2008-01-07 6:56 ` Jan Djärv
2008-01-07 8:23 ` David Kastrup
2008-01-07 14:28 ` Bill Wohler
2008-01-10 4:11 ` Giorgos Keramidas
2008-01-05 22:23 ` Robert J. Chassell
2008-01-05 22:23 ` Robert J. Chassell
2008-01-05 23:05 ` Óscar Fuentes
2008-01-05 23:20 ` Lennart Borgman (gmail)
2008-01-06 17:13 ` Óscar Fuentes
2008-01-06 20:15 ` Stefan Monnier
2008-01-06 20:37 ` Óscar Fuentes
2008-01-06 22:17 ` Bastien
2008-01-05 5:20 ` Eric S. Raymond
2008-01-05 11:17 ` Alan Mackenzie
2008-01-05 14:57 ` Eric S. Raymond
2008-01-05 15:51 ` Lennart Borgman (gmail)
2008-01-05 16:07 ` Eric S. Raymond
2008-01-05 19:58 ` Chris Ball
2008-01-05 20:50 ` Lennart Borgman (gmail)
2008-01-05 21:26 ` Eric S. Raymond
2008-01-05 23:46 ` Stephen J. Turnbull
2008-01-06 16:38 ` email-based development (was:: Why Emacs needs a modern bug tracker) John S. Yates, Jr.
2008-01-05 8:51 ` Let a QA department into the works Andreas Röhler
2008-01-05 14:53 ` Eli Zaretskii
2008-01-06 8:09 ` Richard Stallman
2008-01-06 11:15 ` David Kastrup
2008-01-06 19:52 ` Andreas Röhler
2008-01-05 21:39 ` Why Emacs needs a modern bug tracker Bastien
2008-01-05 14:30 ` Richard Stallman
2008-01-05 15:25 ` Eric S. Raymond
2008-01-06 10:47 ` Richard Stallman
2008-01-05 15:57 ` Eli Zaretskii
2008-01-05 18:24 ` Eric S. Raymond
2008-01-05 20:19 ` Eli Zaretskii
2008-01-05 21:48 ` Eric S. Raymond
2008-01-05 23:21 ` Eli Zaretskii
2008-01-05 23:39 ` Eric S. Raymond
2008-01-06 1:03 ` Nick Roberts
2008-01-06 2:08 ` Miles Bader
2008-01-06 4:08 ` Nick Roberts
2008-01-06 10:26 ` Andreas Schwab
2008-01-06 11:22 ` Nick Roberts
2008-01-06 13:19 ` Andreas Schwab
2008-01-06 11:13 ` David Kastrup
2008-01-06 15:59 ` Eric S. Raymond
2008-01-07 11:30 ` Richard Stallman
2008-01-07 13:29 ` Eric S. Raymond
2008-01-08 19:06 ` Richard Stallman
2008-01-09 15:35 ` Bill Wohler
2008-01-06 4:14 ` Eli Zaretskii
2008-01-06 5:30 ` Miles Bader
2008-01-07 14:40 ` Yavor Doganov
2008-01-10 4:23 ` Giorgos Keramidas
2008-01-10 6:46 ` Mark Linimon
2008-01-11 7:00 ` Bill Wohler
2008-01-11 15:54 ` Óscar Fuentes
2008-01-11 20:42 ` Ralf Angeli
2008-01-11 21:25 ` Nick Roberts
2008-01-11 22:41 ` David Kastrup
2008-01-11 23:14 ` Evans Winner
2008-01-13 8:35 ` Richard Stallman
2008-01-06 18:09 ` Richard Stallman
2008-01-06 20:02 ` Martin Geisler
2008-01-07 11:31 ` Richard Stallman
2008-01-06 20:09 ` Eli Zaretskii
2008-01-06 21:08 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85abnihl6z.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=ams@gnu.org \
--cc=codermattie@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).