unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: John <jmg3000@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs bindings in other programs
Date: Wed, 31 Oct 2007 00:15:51 -0000	[thread overview]
Message-ID: <1193789751.765503.186620@22g2000hsm.googlegroups.com> (raw)
In-Reply-To: <1193416413.534581.16220@v3g2000hsg.googlegroups.com>

On Oct 26, 12:33 pm, YSK <koyf...@gmail.com> wrote:
> [...] getting all other
> programs in my Linux PC to work with Emacs keybindings (particularly
> the navigation ones, C-e, C-a, C-n, C-p, C-k).

I know what you mean. Frequently I go from Emacs to, say, Firefox, and
accidentally hit Emacs keys causing FF to try and print pages, open
new windows, select all, and so on. Actually, for FF, there's an
extension called Firemacs that might be interesting.

Anyhow, I think this is part of the reason there's so many tools
written for use within Emacs. For example, you mention your Java-based
mail client: you might have a look at Emacs' built-in email client
"rmail" as a possible replacement which would allow you to use the
familiar Emacs key combos. I'm guessing the EmacsWiki has info on many
such replacement elisp apps.

Regarding OO.o, the only thing I can suggest is that you look into
alternatives that allow you to edit raw text. For example, you could
try Plain TeX or LaTeX. Or maybe use some generic markup format for
your docs, like reStructuredText ("reST"), asciidoc, Perl 6 Pod,
Markdown, etc. With reST, there's a rst2odt.py tool to convert to OO.o
document format (though it's still fairly new).

---John

  parent reply	other threads:[~2007-10-31  0:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 16:33 Emacs bindings in other programs YSK
2007-10-27  0:29 ` Xah Lee
2007-10-28  3:55   ` YSK
2007-10-31  0:15 ` John [this message]
2007-10-31  7:27   ` Sebastian Tennant
2007-10-31  7:47   ` Martin Rubey
2007-10-31 16:30     ` Stefan Monnier
2007-10-31 17:52       ` Martin Rubey
2007-10-31 20:06         ` Joel J. Adamson
2007-11-02  1:23         ` Stefan Monnier
2007-11-03  0:37         ` Tim X
2007-11-05 23:02           ` David Kastrup
2007-11-23  0:20           ` David Combs
2007-11-23  5:05             ` Tim X
2007-10-31 18:16     ` Amy Templeton
     [not found]     ` <mailman.2805.1193854394.18990.help-gnu-emacs@gnu.org>
2007-10-31 19:06       ` Rajappa Iyer
2007-10-31 14:12   ` Joel J. Adamson
2007-10-31 14:14   ` Joel J. Adamson
2007-10-31 18:11     ` YSK
2007-10-31 18:15   ` YSK
2007-10-31 19:19     ` Sven Bretfeld
2007-10-31 20:08     ` Joel J. Adamson
2007-12-04 13:08       ` Sebastian Tennant
     [not found]       ` <mailman.4489.1196774026.18990.help-gnu-emacs@gnu.org>
2007-12-04 14:46         ` Joel J. Adamson
2007-12-04 20:55           ` Sebastian Tennant
2007-12-04 19:56         ` Malte Spiess
2007-12-04 22:02           ` Sebastian Tennant
2007-12-16 19:05           ` David Combs
2007-12-17 20:51             ` Malte Spiess
     [not found]     ` <mailman.2808.1193858401.18990.help-gnu-emacs@gnu.org>
2007-10-31 20:22       ` YSK
2007-11-01  3:20     ` Alok G. Singh
     [not found]     ` <mailman.2824.1193886791.18990.help-gnu-emacs@gnu.org>
2007-11-06 21:31       ` YSK

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=1193789751.765503.186620@22g2000hsm.googlegroups.com \
    --to=jmg3000@gmail.com \
    --cc=help-gnu-emacs@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.
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).