From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: gnu vs. xemacs
Date: Wed, 27 Dec 2006 14:10:51 +0100 [thread overview]
Message-ID: <FE94C037-172F-4D04-8FAD-18CA109DF520@Web.DE> (raw)
In-Reply-To: <1167219981.424569.215160@73g2000cwn.googlegroups.com>
Am 27.12.2006 um 12:46 schrieb H.:
> I was just curious why people in this community prefer gnu over
> xemacs,
> or if that is the case, and, whatever your preference is, why you feel
> that way. I'm neutral myself, being just a beginner. All opinions
> welcome. For instance, perhaps these difference forks are good for
> different things...?
GNU Emacs uses the key bindings I am used to.
It can be compiled as Carbon Emacs, X11 client in so many tastes,
COCOA/OPENSTEP application, and as non-windowing programme for
Terminal or xterm on Mac OS X.
--
Greetings
Pete
“I hope to die before I *have* to use Microsoft Word.”
- Donald E. Knuth, 2001-10-02 in Tübingen.
next prev parent reply other threads:[~2006-12-27 13:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 11:46 gnu vs. xemacs H.
2006-12-27 12:57 ` Lennart Borgman (gmail)
2006-12-27 13:10 ` Peter Dyballa [this message]
2006-12-27 13:59 ` Sven Bretfeld
2006-12-28 10:27 ` Ramprasad
[not found] ` <mailman.2429.1167301573.2155.help-gnu-emacs@gnu.org>
2006-12-28 11:27 ` Tim X
2006-12-28 18:57 ` Matthew Flaschen
[not found] ` <mailman.2457.1167332268.2155.help-gnu-emacs@gnu.org>
2006-12-28 23:53 ` Tim X
2006-12-29 1:12 ` Leo
2006-12-29 12:46 ` "MIT/GNU/Linux" (was: gnu vs. xemacs) B. Smith-Mannschott
2006-12-29 13:59 ` Micha Feigin
2006-12-29 14:17 ` Gian Uberto Lauri
2006-12-29 17:27 ` "MIT/GNU/Linux" Alexey Pustyntsev
2006-12-29 18:35 ` "MIT/GNU/Linux" Kim F. Storm
[not found] ` <mailman.2488.1167400944.2155.help-gnu-emacs@gnu.org>
2006-12-29 15:29 ` "MIT/GNU/Linux" Giorgos Keramidas
2006-12-30 0:28 ` "MIT/GNU/Linux" Tim X
2006-12-30 6:05 ` "MIT/GNU/Linux" Matthew Flaschen
[not found] ` <mailman.2537.1167458715.2155.help-gnu-emacs@gnu.org>
2006-12-30 12:09 ` "MIT/GNU/Linux" Tim X
2006-12-30 17:13 ` "MIT/GNU/Linux" Matthew Flaschen
[not found] ` <mailman.2550.1167498938.2155.help-gnu-emacs@gnu.org>
2006-12-31 2:36 ` "MIT/GNU/Linux" Tim X
2006-12-31 15:42 ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01 2:45 ` "MIT/GNU/Linux" Tim X
2006-12-31 15:34 ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01 2:21 ` "MIT/GNU/Linux" Tim X
2006-12-29 23:12 ` "MIT/GNU/Linux" Jay Belanger
2006-12-30 15:13 ` "MIT/GNU/Linux" Micha Feigin
[not found] ` <mailman.2547.1167491771.2155.help-gnu-emacs@gnu.org>
2006-12-30 17:19 ` "MIT/GNU/Linux" Robert Thorpe
2006-12-30 17:49 ` "MIT/GNU/Linux" (was: gnu vs. xemacs) Robert Thorpe
2006-12-30 19:20 ` Matthew Flaschen
[not found] ` <mailman.2487.1167396377.2155.help-gnu-emacs@gnu.org>
2007-01-03 6:42 ` "MIT/GNU/Linux" Stefan Monnier
2007-01-03 8:17 ` "MIT/GNU/Linux" Drew Adams
2007-01-03 10:03 ` "MIT/GNU/Linux" Matthew Flaschen
[not found] ` <mailman.2685.1167818637.2155.help-gnu-emacs@gnu.org>
2007-01-03 20:33 ` "MIT/GNU/Linux" Stefan Monnier
2007-01-04 9:14 ` "MIT/GNU/Linux" Matthew Flaschen
[not found] ` <mailman.2475.1167354778.2155.help-gnu-emacs@gnu.org>
2006-12-29 18:23 ` gnu vs. xemacs Hadron Quark
2006-12-29 18:32 ` Ralf Angeli
2006-12-27 19:52 ` David Kastrup
2006-12-28 14:36 ` insert name
2006-12-28 20:25 ` David Kastrup
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=FE94C037-172F-4D04-8FAD-18CA109DF520@Web.DE \
--to=peter_dyballa@web.de \
--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).