*** empty log message ***

[gnus] / readme

diff --git a/readme b/readme
index 89b1d8c..568473c 100644 (file)
--- a/readme
+++ b/readme
@@ -1,19 +1,7 @@
-This package contains a pre-release of (ding) Gnus, version 0.5. The
+This package contains a pre-release of (ding) Gnus, version 0.x. The
 lisp directory contains the source lisp files, and the texi directory
 contains an early draft of the Gnus info pages.
 
-IMPORTANT NOTE FOR NNML USERS: If you have used an earlier version of
-this package, you have to do the following:
-
-ESC ESC (load "nnml")
-M-x nnml-generate-nov-databases
-
-nnml will chew on your mail for a while, and then you can use Gnus
-again. Do not attempt to start Gnus before you have done this.
-
-(This note only applies to people who use nnml as a mail backedn.)
-
-
 Gnus is meant to be totally compatible with GNUS. But, alas, it
 probably isn't, which is one of the reasons for this pre-release. 
 
@@ -21,7 +9,7 @@ To use (ding) Gnus you first have to unpack the files, which you've
 obviously done, because you are reading this. 
 
 You should definitely byte-compile the source files. To do that, you
-can simply say "make" in this directory.
+can simply say "gmake" in this directory. (You have to use GNU's make.) 
 
 Then you have to tell Emacs where Gnus is. You might put something
 like
@@ -35,6 +23,9 @@ both use the same function and variable names. If you have been
 running GNUS in your Emacs, you should probably exit that Emacs and
 start a new one to fire up Gnus.
 
+(ding) Gnus does absolutely not work with Emacs 18, and only shakily
+with Emacs 19s before 19.26. So you definitely need a newish Emacs. 
+
 Then you do a `M-x gnus', and everything should... uhm... it should
 work, but it might not. Set `debug-on-error' to t, and mail me the
 backtraces, or, better yet, find out why Gnus does something wrong,
@@ -58,10 +49,8 @@ although they should document all of Gnus, I think.
 I think I have implemented most of the deep-going changes that I'm
 going to. Things that will probably come in the future, but I haven't
 gotten around to yet is asynchronous posting/pre-fetch of headers and
-articles, better digest handling, a hierarchal Newsgroup buffer,
-allowing the user to provide Newsgroup headers from a function, and a
-few other things that I can't think of at the moment. Oh, and the
-mhspool backend doesn't work at all yet.
+articles, better digest handling, a hierarchal Newsgroup buffer, and a
+few other things that I can't think of at the moment.
 
 Send any comments and all your bug fixes/complaints to
 `larsi@ifi.uio.no'.