From: "Paul D. Smith" <psmith@BayNetworks.com>
Cc: robert@steffi.accessone.com, ding@ifi.uio.no
Subject: Re: September Gnus 0.13 is released
Date: Thu, 16 Nov 95 10:27:55 EST [thread overview]
Message-ID: <9511161527.AA07093@lemming.engeast> (raw)
In-Reply-To: <199511161439.PAA21954@ssv4.dina.kvl.dk>
%% Regarding Re: September Gnus 0.13 is released;
%% Per Abrahamsen <abraham@dina.kvl.dk> writes:
RN> the 19.30 stuff that good? What exactly does it allow you to do?
pa> I haven't noticed any significant new features, beside the new
pa> Gnus. See the appended NEWS file.
There are some very nice new features, but nothing astounding: remember
that 19.29 introduced support for large buffers (up to 133M) which some
people have been asking for for many years, and if you're at 19.28 you
have to consider the features of 19.29 as well in deciding to upgrade.
19.29 also introduced Motif support, but it's pretty yucky and I don't
know anyone who prefers it to Athena.
The main advantage from my perspective (working with the 19.30 pretests)
is that 19.30 is _fast_! Although I installed 19.29 here, I didn't feel
comfortable making it the default bin/emacs (which is still 19.28)
because it was too slow, esp. when you had more than 2-3 frames open.
But 19.30 seems much faster, faster even than I remember 19.28 being.
Part of it no doubt has to do with font-lock improvements; font-locking
a buffer is very quick now. Also the paren-matching code is much
faster: in 19.29 turning it on meant that you could type ahead by
as much as 2-3 lines if you can type fast enough without pausing--very
annoying! I can rarely typeahead on 19.30: the only time being when I
type through an autosave or something. So far, I _like_ it! :)
FWIW.
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> Network Management Development
Senior Software Engineer Bay Networks, Inc.
-----------------------------------------------==<http://www.baynetworks.com/>-
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
next prev parent reply other threads:[~1995-11-16 15:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-15 20:42 Lars Magne Ingebrigtsen
1995-11-15 22:13 ` Paul J. Sanchez
1995-11-15 22:16 ` Lars Magne Ingebrigtsen
1995-11-16 4:44 ` Robert Nicholson
1995-11-16 5:51 ` Sudish Joseph
1995-11-16 15:31 ` Edward J. Sabol
1995-11-17 0:48 ` Lars Magne Ingebrigtsen
1995-11-17 12:18 ` Greg Stark
1995-11-19 7:43 ` Lars Magne Ingebrigtsen
1996-01-15 8:44 ` Greg Stark
1995-11-17 15:50 ` Edward J. Sabol
1995-11-16 14:39 ` Per Abrahamsen
1995-11-16 15:27 ` Paul D. Smith [this message]
1995-11-16 19:57 ` Stefan Monnier
1995-11-30 18:12 ` vroonhof
1995-11-30 21:13 ` What Gnus version for XEmacs 19.14? Steven L. Baur
1995-12-01 3:57 ` Lars Magne Ingebrigtsen
1995-12-01 3:57 ` September Gnus 0.13 is released Lars Magne Ingebrigtsen
1995-11-16 12:44 ` Stefan Bodewig
1995-11-16 15:22 ` Stefan Bodewig
1995-11-16 17:55 ` Steven L. Baur
1995-11-16 18:21 ` Steven L. Baur
1995-11-17 1:08 ` Lars Magne Ingebrigtsen
1995-11-16 20:55 ` Shane Holder
1995-11-16 22:33 ` Steven L. Baur
1995-11-17 1:14 ` Lars Magne Ingebrigtsen
2002-10-20 20:13 Unknown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9511161527.AA07093@lemming.engeast \
--to=psmith@baynetworks.com \
--cc=ding@ifi.uio.no \
--cc=robert@steffi.accessone.com \
/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 NNTP newsgroup(s).