From: Xavier Maillard <xma@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs 21 or snapshot?
Date: Sat, 5 May 2007 15:28:42 +0200 [thread overview]
Message-ID: <200705051328.l45DSgOP006730@localhost.localdomain> (raw)
In-Reply-To: <85lkg5y28l.fsf@lola.goethe.zz> (message from David Kastrup on Fri, 04 May 2007 00:24:42 +0200)
Xavier Maillard <xma@gnu.org> writes:
> Xavier Maillard <xma@gnu.org> writes:
>
> > Hi Mark,
> >
> > As someone wishing to learn Emacs would you recommend I
> > install Emacs 21 or Emacs-snapshot?
> >
> > You'd better stick with the current stable aka GNU Emacs 21.4
>
> It is so much worse in utf-8 support alone that I wonder what you base
> that recommendation on.
>
> Snapshot is a development version whereas GNU Emacs 21 is a
> *stable* version.
Which does not change the fact that the snapshots have been quite
better and more solid than the "stable" version for years now. In
particular now that snapshots are released as "pretest" releases.
For a newbie, I do not see any benefit in Pre-testing a piece of
software he does not know at all. Though I concede pretest
and/or even the CVS version are really good for experienced users
or people with already some GNU Emacs basics.
Can you point to any area, even a single one, where the
supposed "stability" of Emacs 21.4 leads to better results
than, say, the pretest 22.0.99?
I won't be able to do that since I never ever had a problem with
GNU Emacs 21.x on a GNU/linux platform. Things are quite
different on Hurd though.
Xavier
next prev parent reply other threads:[~2007-05-05 13:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 12:15 Emacs 21 or snapshot? Mark Woodward
2007-05-02 18:21 ` Tom Rauchenwald
2007-05-02 21:52 ` Xavier Maillard
2007-05-03 5:52 ` Kevin Rodgers
[not found] ` <mailman.150.1178147431.32220.help-gnu-emacs@gnu.org>
2007-05-03 9:14 ` David Kastrup
2007-05-03 20:20 ` Xavier Maillard
[not found] ` <mailman.197.1178228441.32220.help-gnu-emacs@gnu.org>
2007-05-03 22:24 ` David Kastrup
2007-05-05 13:28 ` Xavier Maillard [this message]
[not found] ` <mailman.300.1178376206.32220.help-gnu-emacs@gnu.org>
2007-05-05 14:43 ` David Kastrup
2007-05-12 6:31 ` Xavier Maillard
2007-05-12 10:53 ` Maciej Katafiasz
[not found] ` <mailman.556.1178967706.32220.help-gnu-emacs@gnu.org>
2007-05-12 18:51 ` Will Parsons
2007-05-12 19:02 ` David Kastrup
2007-05-15 18:26 ` Will Parsons
2007-05-15 18:46 ` Peter Dyballa
2007-05-15 18:46 ` Lennart Borgman (gmail)
2007-05-13 3:25 ` Giorgos Keramidas
2007-05-15 18:33 ` Will Parsons
2007-05-15 23:39 ` Giorgos Keramidas
[not found] ` <mailman.547.1178957352.32220.help-gnu-emacs@gnu.org>
2007-05-12 9:55 ` David Kastrup
[not found] ` <slrnf3sjbc.4ki.oudeis@isis.thalatta.eme>
2007-05-07 17:49 ` Lennart Borgman (gmail)
[not found] ` <mailman.374.1178560583.32220.help-gnu-emacs@gnu.org>
2007-05-10 17:09 ` Will Parsons
2007-05-11 4:56 ` Stefan Monnier
2007-05-11 17:16 ` Will Parsons
2007-05-11 4:57 ` Stefan Monnier
2007-05-11 17:24 ` Will Parsons
2007-05-04 12:37 ` Hadron
2007-05-04 15:01 ` Sebastian Tennant
[not found] ` <mailman.229.1178291246.32220.help-gnu-emacs@gnu.org>
2007-05-05 1:10 ` David Kastrup
2007-05-05 13:30 ` Xavier Maillard
2007-05-03 10:18 ` Hadron
2007-05-05 1:01 ` Mark Woodward
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=200705051328.l45DSgOP006730@localhost.localdomain \
--to=xma@gnu.org \
--cc=dak@gnu.org \
--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).