Re: September Gnus 0.13 is released

Re: September Gnus 0.13 is released

[Unknown]

X-Geek-3: GE/CS d+(--) s:++>: a C++++$ ULUHO++++$ P+++$ L+++ E+++ 
   W+++$ N+++ K-? !w--- O-? !M-- !V-- PS+ PE- Y+ PGP++ t@ 5++ !X R++ 
   b+++ DI+++ D- G e+++ h+ r++ y+
X-Face:  #q.#]5@vq!Jz+E0t_/;Y^gTjR\T^"B'fbeuVGiyKrvbfKJl!^e|e:iu(kJ6c|QYB57LP*|t&YlP~HF/=h:GA6o6W@I#deQL-%#.6]!z:6Cj0kd#4]>*D,|0djf'CVlXkI,>aV4\}?d_KEqsN{Nnt778"OsbQ["56/!nisvyB/uA5Q.{)gm6?q.j71ww.>b9b]-sG8zNt%KkIa>xWg&1VcjZk[hBQ>]j~`WqXl,y1a!(>6`UM{~'X[Y_,Bv+}=L\SS*mA8=s;!=O`ja|@PEzb&i0}Qp,`Z\:6:OmRi*
X-Organization: University of Massachusetts, Amherst, MA 01003
X-Time: Wed Nov 15 17:57:58 1995
X-Mail-System: Vm 5.95 (beta) for GNU Emacs 19.14 XEmacs Lucid (beta5)
References: <w8sraz9vcmv.fsf@narfi.ifi.uio.no>
From: srivasta@plymouth.pilgrim.umass.edu (Manoj Srivastava)
Date: 15 Nov 1995 17:57:57 -0500
In-Reply-To: Lars Magne Ingebrigtsen's message of Wed, 15 Nov 95 21:42:13 +0100
Message-ID: <gvxenv9o58q.fsf@belthil.pilgrim.umass.edu>
Organization: Project Pilgrim, University of Massachusetts at Amherst
Lines: 60
X-Mailer: September Gnus v0.12

Hi,
         Now also at:
    <URL: ftp://ftp.pilgrim.umass.edu/pub/misc/ding/>
   <URL: http://www.pilgrim.umass.edu/pub/misc/ding/>
 <URL: gopher://gopher.pilgrim.umass.edu/11/pub/misc/ding/>

	Currently on tap:
ding:
total 2410
   8 ./				     8 manual/
   8 ../			     8 refcard/
   0 FAQ@			     8 s-manual/
   8 dgnus-5.0.10-5.0.11.diff.gz    21 sgnus-0.10-0.11.diff.gz
   1 dgnus-5.0.11-5.0.12.diff.gz    12 sgnus-0.11-0.12.diff.gz
   8 faq/			   112 sgnus-0.12-0.13.diff.gz
 416 gnus-5.0.12.tar.gz		   456 sgnus-0.13.tar.gz
1336 icons.tar.gz

ding/faq:
total 349
   8 ./		      23 gnus-faq	 280 gnus-faq.ps
   8 ../	      30 gnus-faq.html

ding/manual:
total 397
   8 ./		       2 gnus_10.html	   5 gnus_2.html       6 gnus_7.html
   8 ../	       2 gnus_11.html	  18 gnus_3.html      11 gnus_8.html
   1 .cache	      26 gnus_12.html	  74 gnus_4.html       6 gnus_9.html
   4 .cache+	      44 gnus_13.html	 128 gnus_5.html      10 gnus_toc.html
  17 gnus_1.html      17 gnus_14.html	  10 gnus_6.html

ding/refcard:
total 291
   8 ./		       32 bk-a4-s1.ps.gz    20 gnusref.tar.gz
   8 ../	       26 bk-a4-s2.ps.gz    21 quickref.ps.gz
   1 .cache	       40 bk-lt-d.ps.gz	    34 refcard.ps.gz
   3 README	       32 bk-lt-s1.ps.gz
  40 bk-a4-d.ps.gz     26 bk-lt-s2.ps.gz

ding/s-manual:
total 465
   8 ./		       2 gnus_12.html	  22 gnus_3.html      33 gnus_8.html
   8 ../	      33 gnus_13.html	  82 gnus_4.html      19 gnus_9.html
  18 gnus_1.html      51 gnus_14.html	 128 gnus_5.html      11 gnus_toc.html
   6 gnus_10.html     18 gnus_15.html	  10 gnus_6.html
   3 gnus_11.html      5 gnus_2.html	   8 gnus_7.html

	manoj

-- He experienced that nervous agitation to which brave men as well as
 cowards are subject; with this difference, that the one sinks under
 it, like the vine under the hailstorm, and the other collects his
 energies to shake it off, as the cedar of Lebanon is said to elevate
 its boughs to disperse the shower which accumulates upon them.  --
 Sir Walter Scott

Manoj Srivastava         Project Pilgrim, Department of Computer Science 
Phone: (413) 545-3918             A143B Lederle Graduate Research Center
Fax: (413) 545-1249       University of Massachusetts, Amherst, MA 01003     
email:srivasta@pilgrim.umass.edu http://www.pilgrim.umass.edu/~srivasta/

Re: September Gnus 0.13 is released

[Greg Stark]

>    Since new Emacs releases are free, I think sysadms should get with the
>    program and install Newer & Fresher Emacs releases as soon as they
>    come out, myself.  That's easy enough for me to say, and it leaves
>    some users who have intractible sysadms hanging, but it's a hard,
>    cruel world.  And I'm just doing my best to make it a harder, crueller
>    world. 

You thin that's bad (not installing 19.29 yet) the punch line is that the
default version of Emacs around here is still 18.59. sigh.

--
greg

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

vroonhof@math.ethz.ch writes:

> I consider it a mistake to ship packages that don't support XE with E
> and vice versa, because it makes library sharing betweem them
> unnecesairily difficult for some small savings in discspace.

The word from the XEmacs people is that it's quite likely that Emacs
and XEmacs byte-code will diverge in the future, so one will really
have to keep separate Elisp trees for Emacs and XEmacs.

-- 
Home is where the cat is.

Re: September Gnus 0.13 is released

[vroonhof]

Dear Lars and ding list readers (Note that I only occasionally browse
the list)

>>>>> "Per" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

    Per> 5.0.12 is the release at Lars' site.  Emacs 19.30 will have
    Per> 5.1.  I'm more curious about what will be in XEmacs 19.14.
    Per> It might be a good idea to make an unbundled 5.1.1 release
    Per> after Emacs 19.30 has been released.

Now that 19.30 is out. I am even more for such an unbundled release.
I want the bug fixes in 5.1 without getting the whole 19.30
distribution. At the moment I don't want to ask our sysadmin people to
upgrade our 19.28, because it is difficult enough even to get them to
do more urgent things.

Besides, I discovered enough discspace to install my own (self
maintained) copy of XEmacs 19.13 and really am thinking of switching
now. So having an up to date copy of a stable gnus with XEmacs support
would be nice.

I consider it a mistake to ship packages that don't support XE with E
and vice versa, because it makes library sharing betweem them
unnecesairily difficult for some small savings in discspace.

Enyoing GNUS very much, thank you,

Jan

P.S. Where did the versionnumber in the (nice) startup screen go?

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

gsstark@MIT.EDU (Greg Stark) writes:

> I'ld like to point out that it's not just 19.28 support you're dropping,
> if compiled under 19.28 it works find under at least 19.25 -- 19.29.
> 
> Here some machines run 19.25, some 19.28 and some 19.29, and I've
> been able to support all of these by building sgnus and gnus 5 under
> Emacs 19.28.

Since new Emacs releases are free, I think sysadms should get with the
program and install Newer & Fresher Emacs releases as soon as they
come out, myself.  That's easy enough for me to say, and it leaves
some users who have intractible sysadms hanging, but it's a hard,
cruel world.  And I'm just doing my best to make it a harder, crueller
world. 

> There's really no excuse for using `(foo) in code that isn't part of Emacs
> itself.

Of course there is.  It's prettier.

-- 
Home is where the cat is.

Re: September Gnus 0.13 is released

[Edward J. Sabol]

Excerpts from mail: (17-Nov-95) Re: September Gnus 0.13 is released by Lars Magne Ingebrigtsen
> So, like, 19.28 people can get by with 5.0.12. It's a working Gnus.
> September Gnus is alpha, and has quite a lot of neat stuff in it, but
> there's nothing really Earth-shattering about it.

Well, speaking as someone who's been using September Gnus since it's
inception, the prospect of going back to Gnus 5.0.12 is not something I look
forward to. I'll probably stay with September Gnus 0.12, bugs and all.

Still, I understand your reasons, and I agree with them. I'd probably do the
same thing. That's not going to stop me from complaining about it though.

And it'll probably take longer than a month for the FSF to release 19.30, and
when you factor in the time it will take my sysadmins to install it, it'll be
a good two months...

Re: September Gnus 0.13 is released

[Greg Stark]

>   I just find it a lot easier to write code when I don't have to wrap
>   everything in `(and (fboundp))'.  When I write ugly code I get
>   depressed.  So I write less code.  Being able to say "`(list ,my)"
>   instead of "(` (list (, my)))" is a great relief.  :-)
>
>   So, like, 19.28 people can get by with 5.0.12.  It's a working Gnus.
>   September Gnus is alpha, and has quite a lot of neat stuff in it, but
>   there's nothing really Earth-shattering about it.

I'ld like to point out that it's not just 19.28 support you're dropping,
if compiled under 19.28 it works find under at least 19.25 -- 19.29.

Here some machines run 19.25, some 19.28 and some 19.29, and I've been able to
support all of these by building sgnus and gnus 5 under Emacs 19.28. 

There's really no excuse for using `(foo) in code that isn't part of Emacs
itself.  The support for the syntax was intented largely for compatibility
with code written for XEmacs or for Common Lisp code.  Writing new code using
it is just pointlessly writing unportable code.

If anything it makes _more_ sense for September Gnus to be written portably
than Gnus 5 since Gnus 5 is packaged with Emacs and September Gnus is only
usable as a separate package.  

greg

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

steve@miranova.com (Steven L. Baur) writes:

>     Shane> It also appears that followup `f', `F' is broken in .13 for
>     Shane> mail also at least for nnml.  Followup no longer includes
>     Shane> CC's and tries to treat mail folders as news groups, by
>     Shane> inserting
> 
>     Shane> Newsgroup: <foldername>
> 
>     Shane> as a header.
> 
> I only see the behavior you describe if to-address is not set in the
> group parameters.  With to-address set, it appears to behave smoothly.
> 
> I'm not sure whether this is a bug or not, but given how I use
> folders, this is *most* useful behavior.  Was this intentional Lars?

Nope, it was a bug, I'm afraid.  :-)  Fix in 0.14.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

steve@miranova.com (Steven L. Baur) writes:

> Ouch.  0.13 has killed all my ticks too (after downgrading back to
> 0.12).  :-(.

Uhm.  Sorry.  I forgot to mention that going from 0.13 to, well,
anything older is totally poison.  

The reason for this strange behavior is that dormant and ticked
articles used to be subsets of the unread articles.  This led to all
kinds of twiddly programming.  I don't like twiddly programming, so in
0.13 they are now ordinary marks lists, just like bookmarks, expirable
marks, etc.  Much cleaner. 

However, it's only possible to go from the old version to the new, not
the other way around.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

"Edward J. Sabol" <sabol@thuban.gsfc.nasa.gov> writes:

> Ditto! I'm locked into 19.28 for the forseeable future, at least until 19.30
> is released, and I'm guessing that won't be for another month or more, if
> we're lucky.

Well, a month isn't that long.  It's been a two-week gap between 0.12
and 0.13.  Time flies.

I just find it a lot easier to write code when I don't have to wrap
everything in `(and (fboundp))'.  When I write ugly code I get
depressed.  So I write less code.  Being able to say "`(list ,my)"
instead of "(` (list (, my)))" is a great relief.  :-)

So, like, 19.28 people can get by with 5.0.12.  It's a working Gnus.
September Gnus is alpha, and has quite a lot of neat stuff in it, but
there's nothing really Earth-shattering about it.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: September Gnus 0.13 is released

[Steven L. Baur]

>>>>> "Shane" == Shane Holder <holder@convex.com> writes:

>>>>> "Stefan" == Stefan Bodewig <stefan@marvin.fkphy.uni-duesseldorf.de> writes:
    Stefan> First and worst: I cannot post articles (neither `a' nor
    Stefan> `f' nor `F' works) because:

    Shane> It also appears that followup `f', `F' is broken in .13 for
    Shane> mail also at least for nnml.  Followup no longer includes
    Shane> CC's and tries to treat mail folders as news groups, by
    Shane> inserting

    Shane> Newsgroup: <foldername>

    Shane> as a header.

I only see the behavior you describe if to-address is not set in the
group parameters.  With to-address set, it appears to behave smoothly.

I'm not sure whether this is a bug or not, but given how I use
folders, this is *most* useful behavior.  Was this intentional Lars?

Regards,
-- 
steve@miranova.com baur

Re: September Gnus 0.13 is released

[Shane Holder]

>>>>> "Stefan" == Stefan Bodewig <stefan@marvin.fkphy.uni-duesseldorf.de> writes:

Stefan> First and worst: I cannot post articles (neither `a' nor `f' nor `F'
Stefan> works) because:

It also appears that followup `f', `F' is broken in .13 for mail also
at least for nnml.  Followup no longer includes CC's and tries to
treat mail folders as news groups, by inserting 

Newsgroup: <foldername>

as a header.

Shane

-- 
Shane Holder         | e-mail: holder@convex.com
Convex Computer Corp | phone: (214)497-4182
3000 Waterview       | So, if I work my 40 hours with out sleeping,
Richardson, TX 75083 | can I have the rest of the week off?

Re: September Gnus 0.13 is released

[Stefan Monnier]

> because it was too slow, esp. when you had more than 2-3 frames open.

This was only the case when you had the menu bar and font-lock.
But it was a bug nonetheless.

> 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! :)

It's still very easy to type ahead: you only have to have two frames open on the
same buffer.


	Stefan

Re: September Gnus 0.13 is released

[Steven L. Baur]

>My second problem: My mail has lost all the nice expireable-marks and
>whatever I do they don't want to come back.

Ouch.  0.13 has killed all my ticks too (after downgrading back to
0.12).  :-(.

-- 
steve@miranova.com baur

Re: September Gnus 0.13 is released

[Steven L. Baur]

>>>>> "Stefan" == Stefan Bodewig <stefan@marvin.fkphy.uni-duesseldorf.de> writes:

    Stefan> Hi, I have two rather large problems with 0.13.


    Stefan> My second problem: My mail has lost all the nice
    Stefan> expireable-marks and whatever I do they don't want to come
    Stefan> back. Mark them with `E', leave group, reenter and see:
    Stefan> They are marked with an O. Don't know, if this is nnbabyl
    Stefan> specific.

It's not.  I've experienced the same thing with nnml.  All of the Gnus
code that references the Group info was changed, and the announcement
did warn of potential problems in this area:

>You'll also get incorrect article counts in the group buffer before
>entering/exiting the groups.  This will resolve itself after a while
>-- you don't have to do anything in particular.

-- 
steve@miranova.com baur

Re: September Gnus 0.13 is released

[Edward J. Sabol]

Excerpts from mail: (16-Nov-95) Re: September Gnus 0.13 is released by Sudish Joseph
>> Anybody want to try and convince lars to keep 19.28 support in? Is the
>> 19.30 stuff that good? What exactly does it allow you to do?
> If it's a vote to keep 19.28 support in, I vote for yes. :-) But I
> doubt it's a vote...I guess I'll be staying at 0.12 for a long time. :(

Ditto! I'm locked into 19.28 for the forseeable future, at least until 19.30
is released, and I'm guessing that won't be for another month or more, if
we're lucky.

Later,
Ed

Re: September Gnus 0.13 is released

[Paul D. Smith]

%% 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.

Re: September Gnus 0.13 is released

[Stefan Bodewig]

>>>>> "SB" == Stefan Bodewig <stefan@marvin.fkphy.uni-duesseldorf.de> writes:

 SB> A quick hack to get my articles posted was to include
 SB> mail-header-separator into the header region by deleting the
 SB> match-beginnig part in gnus-inews-narrow-to-headers. Probably
 SB> this will totaly crash Gnus somewhere else.

In fact, it does. I couldn't even send my articles after I had written
them. insert-headers failed. Defined my own narrow-to-headers and now
call this from ..-bfcc. Still an awfull hack.

Stefan

Re: September Gnus 0.13 is released

[Per Abrahamsen]

>>>>> "RN" == Robert Nicholson <robert@steffi.accessone.com> writes:

RN> With respect to 5.0.12.

RN> I take it this is that one that FSF maintain now. Probably in their
RN> own time. ie. not released separately to Emacs?

5.0.12 is the release at Lars' site.  Emacs 19.30 will have 5.1.  I'm
more curious about what will be in XEmacs 19.14.  It might be a good
idea to make an unbundled 5.1.1 release after Emacs 19.30 has been
released.

RN> Anybody want to try and convince lars to keep 19.28 support in? 

I'd vote no for two reasons: One, maintaining support for old versions
slow down development and two, there is already a good alternative for
people using Emacs 19.28 (people using 19.22 or 18.55 are much worse
of). 

RN> the 19.30 stuff that good? What exactly does it allow you to do?

I haven't noticed any significant new features, beside the new Gnus.
See the appended NEWS file.

SJ> It'd be nice if someone pointed out what new feature of 19.29 it is
SJ> that ding is using, so that we may work around that and still upgrade.

That the `intangible' property exists but doesn't work has been the
largest problem in my code.

\f
* Editing Changes in Emacs 19.30.

** Be sure to recompile your byte-compiled Emacs Lisp files
if you last compiled them with Emacs 19.28 or earlier.
You can use M-x byte-force-recompile to recompile all the .elc files
in a specified directory.

** Emacs now provides multiple-frame support on Windows NT
and Windows 95.

** M-x column-number-mode toggles a minor mode which displays
the current column number in the mode line.

** Line Number mode is now enabled by default.

** C-mouse-1 now once again provides a menu of buffers to select.
S-mouse-1 is now the way to select a default font for the frame.

** If you type a M-x command that has an equivalent key binding,
the equivalent is shown in the minibuffer before the command executes.
This feature is enabled by default for the sake of beginning users.
You can turn the feature off by setting suggest-key-bindings to nil.

** M-x what-line now displays the line number in the accessible
portion of the buffer as well as the line number in the full buffer,
when narrowing is in effect.

** The menu bar is now visible on text-only terminals.  To choose a
command from the menu bar when you have no mouse, type M-`
(Meta-Backquote).

** Whenever you invoke a minibuffer, it appears in the minibuffer
window that the current frame uses.

Emacs can only use one minibuffer window at a time.  If you activate
the minibuffer while a minibuffer window is active in some other
frame, the outer minibuffer window disappears while the inner one is
active.

** Echo area messages always appear in the minibuffer window that the
current frame uses.  If a minibuffer is active in some other frame,
the echo area message does not hide it even temporarily.

** Dead-key and composite character processing is done in the standard
X11R6 manner (through the default "input method" using the
/usr/lib/X11/locale/*/Compose databases of key combinations).  I.e. if
it works in xterm, it should also work in emacs now.

** Mouse changes

*** There is a new mouse-scroll-min-lines variable to control the
minimum number of lines scrolled by dragging the mouse outside a
window's edge.

*** Dragging mouse-1 on a vertical line that separates windows
now moves the line, thus changing the widths of the two windows.
(This feature is available only if you don't have vertical scroll bars.
If you do use them, a scroll bar separates two side-by-side windows.)

*** Double-click mouse-1 on a character with "symbol" syntax (such as
underscore, in C mode) selects the entire symbol surrounding that
character.  (Double-click mouse-1 on a letter selects a whole word.)

** The CC-mode package now provides the default C and C++ modes.
See the manual for documentation of its features.

** Filling changes.

*** If the variable colon-double-space is non-nil, the explicit fill
commands put two spaces after a colon.

*** Auto-Fill mode now supports Adaptive Fill mode just as the
explicit fill commands do.  The variable adaptive-fill-regexp
specifies a regular expression to match text at the beginning of
a line that should be the fill prefix.

*** Adaptive Fill mode can take a fill prefix from the first line of a
paragraph, *provided* that line is not a paragraph-starter line.

Paragraph-starter lines are indented lines that start a new
paragraph because they are indented.  This indentation shouldn't
be copied to additional lines.

Whether indented lines are paragraph lines depends on the value of the
variable paragraph-start.  Some major modes set this; you can set it
by hand or in mode hooks as well.  For editing text in which paragraph
first lines are not indented, and which contains paragraphs in which
all lines are indented, you should use Indented Text mode or arrange
for paragraph-start not to match these lines.

*** You can specify more complex ways of choosing a fill prefix
automatically by setting `adaptive-fill-function'.  This function
is called with point after the left margin of a line, and it should
return the appropriate fill prefix based on that line.
If it returns nil, that means it sees no fill prefix in that line.

** When incremental search wraps around to the beginning (or end) of
the buffer, if you keep on searching until you go past the original
starting point of the search, the echo area changes from "Wrapped" to
"Overwrapped".  That tells you that you are revisiting matches that
you have already seen.

** Gnus changes.

Gnus, the Emacs newsreader, has been rewritten and expanded.  Most
things that worked with the old version should still work with the new
version.  Code that relies heavily on Gnus internals is likely to
fail, though.

*** Incompatabilities with the old GNUS.

**** All interactive commands have kept their names, but many internal
functions have changed names.

**** The summary mode gnus-uu commands have been moved from the `C-c
C-v' keymap to the `X' keymap.

**** There can now be several summary buffers active at once.
Variables that are relevant to each summary buffer are buffer-local to
that buffer.

**** Old hilit code doesn't work at all.  Gnus performs its own
highlighting based not only on what's visible in the buffer, but on
other data structures.

**** Old packages like `expire-kill' will no longer work.  

**** `C-c C-l' in the group buffer no longer switches to a different
buffer, but instead lists killed groups in the group buffer.

*** New features.

**** The look of all buffers can be changed by setting format-like
variables.
 
**** Local spool and several NNTP servers can be used at once.

**** Groups can be combined into virtual groups.

**** Different mail formats can be read much the same way as one would
read newsgroups.  All the mail backends implement mail expiry schemes.

**** Gnus can use various strategies for gathering threads that have
lost their roots (thereby gathering loose sub-threads into one thread)
or it can go back and retrieve enough headers to build a complete
thread.

**** Killed groups can be read.

**** Gnus can do partial group updates - you do not have to retrieve
the entire active file just to check for new articles in a few groups.

**** Gnus implements a sliding scale of subscribedness to groups.

**** You can score articles according to any number of criteria.  You
can get Gnus to score articles for you using adaptive scoring.

**** Gnus maintains a dribble buffer that is auto-saved the normal
Emacs manner, so it should be difficult to lose much data on what you
have read if your machine should go down.

**** Gnus now has its own startup file (`.gnus.el') to avoid
cluttering up the `.emacs' file.

**** You can set the process mark on both groups and articles and
perform operations on all the marked items.

**** You can grep through a subset of groups and create a group from
the results.

**** You can list subsets of groups using matches on group names or
group descriptions.

**** You can browse foreign servers and subscribe to groups from those
servers.

**** Gnus can pre-fetch articles asynchronously on a second connection
to the servers.

**** You can cache articles locally.

**** Gnus can fetch FAQs to and descriptions of groups.

**** Digests (and other files) can be used as the basis for groups.

**** Articles can be highlighted and customized.

** Changes to Version Control (VC)

*** General changes (all backends).

VC directory listings (C-x v d) are now kept up to date when you do a
vc-next-action (C-x v v) on the marked files.  The `g' command updates
the buffer properly.  `=' in a VC dired buffer produces a version
control diff, not an ordinary diff.

*** CVS changes.

Under CVS, you no longer need to type C-x C-q before you can edit a
file.  VC doesn't write-protect unmodified buffers anymore; you can
freely change them at any time.  The mode line keeps track of the
file status.

If you do want unmodified files to be write-protected, set your
CVSREAD environment variable.  VC sees this and behaves accordingly;
that will give you the behaviour of Emacs 19.29, similar to that under
RCS and SCCS.  In this mode, if the variable vc-mistrust-permissions
is nil, VC learns the modification state from the file permissions.
When setting CVSREAD for the first time, you should check out the
whole module anew, so that the file permissions are set correctly.

VC also works with remote repositories now.  When you visit a file, it
doesn't run "cvs status" anymore, so there shouldn't be any long delays.

Directory listings under VC/CVS have been enhanced.  Type C-x v d, and
you get a list of all files in or below the current directory that are
not up-to-date.  The actual status (modified, merge, conflict, ...) is
displayed for each file.  If you give a prefix argument (C-u C-x v d),
up-to-date files are also listed.  You can mark any number of files,
and execute the next logical version control command on them (C-x v v).

*** Starting a new branch.

If you try to lock a version that is not the latest on its branch, 
VC asks for confirmation in the minibuffer.  If you say no, it offers
to lock the latest version instead.

*** RCS non-strict locking.

VC can now handle RCS non-strict locking, too.  In this mode, working
files are always writable and you needn't lock the file before making
changes, similar to the default mode under CVS.  To enable non-strict
locking for a file, use the "rcs -U" command.

*** Sharing RCS master files.

If you share RCS subdirs with other users (through symbolic links),
and you always want to work on the latest version, set
vc-consult-headers to nil and vc-mistrust-permissions to `t'.
Then you see the state of the *latest* version on the mode line, not
that of your working file.  When you do a check out, VC overwrites
your working file with the latest version from the master.

*** RCS customization.

There is a new variable vc-consult-headers.  If it is t (the default),
VC searches for RCS headers in working files (like `$Id$') and
determines the state of the file from them, not from the master file.
This is fast and more reliable when you use branches.  (The variable
was already present in Emacs 19.29, but didn't get mentioned in the
NEWS.)

** The uniquify package chooses buffer names differently when you
visit multiple files with the same name (in different directories).

** RMAIL now always uses the movemail program when it renames an
inbox file, so that it can interlock properly with the mailer
no matter where it is delivering mail.

** The environment variable NAME, if set, now specifies the value of
(user-full-name), when Emacs starts up.

** tex-start-of-header and tex-end-of-header are now regular expressions,
not strings.

** To enable automatic uncompression of compressed files,
type M-x auto-compression-mode.  (This command used to be called
toggle-auto-compression, but was not documented before.)  In Lisp,
you can do

   (auto-compression-mode 1)

to turn the mode on.

** The new pc-select package emulates the key bindings for cutting and
pasting, and selection of regions, found in Windows, Motif, and the
Macintosh.

** TPU-edt Changes

Loading tpu-edt no longer turns on tpu-edt mode.  In fact, it is no
longer necessary to explicitly load tpu-edt.  All you need to do to
turn on tpu-edt is run the tpu-edt function.  Here's how to run
tpu-edt instead of loading the file:
  
  Running Emacs:   Type      emacs -f tpu-edt
                    not      emacs -l tpu-edt

  Within Emacs:    Type      M-x tpu-edt <ret>
                    not      M-x load-library <ret> tpu-edt <ret>
  
  In .emacs:       Use       (tpu-edt)
                   not       (load "tpu-edt")
  
The default name of the tpu-edt X key definition file has changed from
~/.tpu-gnu-keys to ~/.tpu-keys.  If you don't rename the file yourself,
tpu-edt will offer to rename it the first time you invoke it under
x-windows.

** The files etc/termcap.dat and etc/termcap.ucb have been replaced
with a new, merged, and much more comprehensive termcap file.  The
new file should include all the special entries from the old one.
This new file is under active development as part of the ncurses
project.  If you have any questions about this file, or problems with
an entry in it, email terminfo@ccil.org.

** The minibuffer now has a menu-bar menu.  You can use it to exit or
abort the minibuffer, or to ask for completion.

** Help buffers now use a special major mode, Help mode.  This mode
normally turns on View mode; it also provides a hook, help-mode-hook,
which you can use for other customization.

** Font Lock mode

*** Supports Scheme, TCL and Help modes

For example, to automatically turn on Font Lock mode in the *Help*
buffer, put:

 (add-hook 'help-mode-hook 'turn-on-font-lock)

in your ~/.emacs.

*** Enhanced fontification

The structure of font-lock-keywords is extended to allow "anchored" keywords.
Typically, a keyword item of font-lock-keywords comprises a regexp to search
for and information to specify how the regexp should be highlighted.  However,
the highlighting information is extended so that it can be another keyword
item.  This keyword item, its regexp and highlighting information, is processed
before resuming with the keyword item of which it is part.

For example, a typical keyword item might be:

 ("\\<anchor\\>" (0 anchor-face))

which fontifies each occurrence of the discrete word "anchor" in the value of
the variable anchor-face.  However, the highlighting information can be used to
fontify text that is anchored to the word "anchor".  For example:

 ("\\<anchor\\>" (0 anchor-face) ("\\=[ ,]*\\(item\\)" nil nil (1 item-face)))

which fontifies each occurrence of "anchor" as above, but for each occurrence
of "anchor", each occurrence of "item", in any following comma separated list,
is fontified in the value of the variable item-face.  Thus the "item" text is
anchored to the "anchor" text.  See the variable documentation for further
information.

This feature is used to extend the level and quality of fontification in a
number of modes.  For example, C/C++ modes now have level 3 decoration that
includes the fontification of variable and function names in declaration lists.
In this instance, the "anchor" described in the above example is a type or
class name, and an "item" is a variable or function name.

*** Fontification levels

The variables font-lock-maximum-decoration and font-lock-maximum-size are
extended to specify levels and sizes for specific modes.  The variable
font-lock-maximum-decoration specifies the preferred level of fontification for
modes that provide multiple levels (typically from "subdued" to "gaudy").  The
variable font-lock-maximum-size specifies the buffer size for which buffer
fontification is suppressed when Font Lock mode is turned on (typically because
it would take too long).

These variables can now specify values for individual modes, by supplying
lists of mode names and values.  For example, to use the above mentioned level
3 decoration for buffers in C/C++ modes, and default decoration otherwise, put:

 (setq font-lock-maximum-decoration '((c-mode . 3) (c++-mode . 3)))

in your ~/.emacs.  Maximum buffer size values for individual modes are
specified in the same way with the variable font-lock-maximum-size.

*** Font Lock configuration

The mechanism to provide default settings for Font Lock mode are the variables
font-lock-defaults and font-lock-maximum-decoration.  Typically, you should
only need to change the value of font-lock-maximum-decoration.  However, to
support Font Lock mode for buffers in modes that currently do not support Font
Lock mode, you should set a buffer local value of font-lock-defaults for that
mode, typically via its mode hook.

These variables are used by Font Lock mode to set the values of the variables
font-lock-keywords, font-lock-keywords-only, font-lock-syntax-table,
font-lock-beginning-of-syntax-function and font-lock-keywords-case-fold-search.

You need not set these variables directly, and should not set them yourself
since the underlining mechanism may change in future.

** Archive mode is now the default mode for various sorts of
archive files (files whose names end with .arc, .lzh, .zip, and .zoo).

** Apropos now uses faces for legibility.  It also has new features
such as showing plists, and snooping thru values.  It now supports
highlighted mouse-2 or RET hypertext.  All symbol-names start with
`apropos'.

** Skeleton commands now work smoothly as abbrev definitions.  The
element < no longer exists, ' is a new element.

** The autoinsert insert facility for prefilling empty files as soon
as they are found has been extended to accomodate skeletons or calling
functions.  Put (add-hook 'find-file-hooks 'auto-insert) into your
~/.emacs.

** Automatic copyright update functionality is now available for all
documents, not just Emacs Lisp.  Put (add-hook 'write-file-hooks
'copyright-update) into your ~/.emacs.

** Scripts of various languages (Shell, AWK, Perl, makefiles ...) can
be automatically provided with a magic number and be made executable
by their respective modes under control of various user variables.
The mode must call (executable-set-magic "perl") or
(executable-set-magic "make" "-f").  The latter for example has no
effect on [Mm]akefile.

** Shell script mode V2.0 now supports over 15 different shells.
There is also an edit-interpret-debug cycle via C-c !  (from
executable based on compile).  Because of the different detail in
messages, ksh gives the best results (when outside functions), sh and
bash find syntax errors but no command name typos while csh
programmers are left out in the cold.  The new command C-c | executes
the region and optionally beginning of script.

Cases such as `sh' being a `bash' are now accounted for.
Fontification now also does variables, the magic number and all
builtin commands.  Shell script mode no longer mingles `tab-width' and
indentation style.  Var `sh-tab-width' is replaced by
`sh-indentation'.  Empty lines are now indented like previous
non-empty line, rather than just previous line.  It no longer has the
annoying $ variable prompting, it uses `comint-dynamic-completion'
instead for commands, variables & filenames.

** Two-column now automatically scrolls both buffers, eliminating a
few commands dedicated to this.  All symbols start with `2C-'.  The
commands that operate in two-column mode are no longer bound to keys
outside.  f2 o  will now position at the same point in other text.

New command  f2 RET  will also newline where  f2 o  would position.

** MS-DOS Enhancements:

*** Better mouse control by adding the following functions [in dosfns.c]
msdos-mouse-enable, msdos-mouse-disable, msdos-mouse-init.

**** If another foreground/background color than the default is setup in
your ~/_emacs, then the screen briefly flickers with the default
colors before changing to the colors you have specified.  To avoid
this, the EMACSCOLORS environment variable exists.  It shall be
defined as a string with the following elements:
  
    set EMACSCOLORS=fb;fb
  
The first set of "fb" defines the initial foreground and background
colors using standard dos color numbers (0=black,.., 7=white).
If specified, the second set of "fb" defines the colors which are
restored when you leave emacs.
  
*** The new SUSPEND environment variable can now be set as the shell to
use when suspending emacs.  This can be used to override the stupid
limitation on the environment of sub-shells in MS-DOS (they are just
large enough to hold the currently defined variables, not leaving
room for more); to overcome this limitation, add this to autoexec.bat:
  
    set SUSPEND=%COMSPEC% /E:2000

** The escape character can now be displayed (as a tiny left arrow)
on X window frames.  Try this:
    (aset standard-display-table 27 (vector 27))
after first creating a display table.

** The new command-line option --eval specifies an expression to evaluate
from the command line.

** etags has now the ability to tag perl files.  They are recognised
either by the .pm and .pl suffixes or by looking at their first line,
where it looks for a sharp-bang (#!) sequence followed by the
interpreter name.  The tagged lines are those beginning with the `sub'
keyword.  New suffixes recognised are .hpp for C++; .f90 for Fortran;
.bib, .ltx, .TeX for TeX (.bbl, .dtx removed); .ml for Lisp; .prolog
for prolog (.pl is now perl).
\f
* Lisp changes in Emacs 19.30.

** There is a new data type called a char-table which is an array
indexed by a character.  Currently this is mostly equivalent to a
vector of length 256, but in the future, when a wider character set is
in use, it will be different.  To create one, call
   (make-char-table SUBTYPE INITIAL-VALUE)

SUBTYPE is a symbol that identifies the specific use of this
character table.  It can be any of these values:

  syntax-table
  display-table
  keyboard-translate-table
  case-table

The function `char-table-subtype' returns the subtype of a char-table.
You cannot alter the subtype of an existing char-table.

A char-table has an element for each character code.  It also has some
"extra slots".  The number of extra slots depends on the subtype and
their use depends on the subtype.  (Each subtype symbol has a
`char-table-extra-slots' property that says how many extra slots to
make.)  Use (char-table-extra-slot TABLE N) to access extra slot N and
(set-char-table-extra-slot TABLE N VALUE) to store VALUE in slot N.

A char-table T can have a parent, which should be another char-table
P.  If you look for the value in T for character C, and the table T
actually holds nil, P's element for character C is used instead.
The functions `char-table-parent' and `set-char-table-parent'
let you read or set the parent of a char-table.

To scan all the values in a char-table, do not try to loop through all
possible character codes.  That would work for now, but will not work
in the future.  Instead, call map-char-table.  (map-char-table
FUNCTION TABLE) calls FUNCTION once for each character or character
set that has a distinct value in TABLE.  FUNCTION gets two arguments,
RANGE and VALUE.  RANGE specifies a range of TABLE that has one
uniform value, and VALUE is the value in TABLE for that range.

Currently, RANGE is always a vector containing a single character
and it refers to that character alone.  In the future, other kinds
of ranges will occur.  You can set the value for a given range
with (set-char-table-range TABLE RANGE VALUE) and examine the value
for a range with (char-table-range TABLE RANGE).

** A new data type called a bool-vector is a vector of values
that are either t or nil.  To create one, do
   (make-bool-vector LENGTH INITIAL-VALUE)

** Syntax tables are now represented as char-tables.
All syntax tables other than the standard syntax table
normally have the standard syntax table as their parent.
Their subtype is `syntax-table'.

** Display tables are now represented as char-tables.
Their subtype is `display-table'.

** Case tables are now represented as char-tables.
Their subtype is `case-table'.

** The value of keyboard-translate-table may now be a char-table
instead of a string.  Normally the char-tables used for this purpose
have the subtype `keyboard-translate-table', but that is not required.

** The new hook window-scroll-functions is run when a window has been
scrolled.  The functions in this list are called just before
redisplay, after the new window-start has been computed.  Each function
is called with two arguments--the window that has been scrolled, and its
new window-start position.

This hook is useful for on-the-fly fontification and other features
that affect how the redisplayed text will look when it is displayed.

The window-end value of the window is not valid when these functions
are called.  The computation of window-end is byproduct of actual
redisplay of the window contents, which means it has not yet happened
when the hook is run.  Computing window-end specially in advance for
the sake of these functions would cause a slowdown.

The hook functions can determine where the text on the window will end
by calling vertical-motion starting with the window-start position.

** The new hook redisplay-end-trigger-hook is run whenever redisplay
in window uses text that extends past a specified end trigger
position.  You set the end trigger position with the function
set-window-redisplay-end-trigger.  Storing nil for the end trigger position
turns off the feature, and the trigger value is automatically reset to nil
just after the hook is run.

You can use the function window-redisplay-end-trigger to read a
window's current end trigger value.

** The new function insert-file-contents-literally inserts the
contents of a file without any character set translation or decoding.

** You can now specify, for each marker, how it should relocate when
text is inserted at the place where the marker points.  This is called
the "insertion type" of the marker.

To set the insertion type, do (set-marker-insertion-type MARKER TYPE).
If TYPE is t, it means the marker advances when text is inserted.  If
TYPE is nil, it means the marker does not advance.  (In Emacs 19.29,
markers did not advance.)

The function marker-insertion-type reports the insertion type of a
given marker.  The function copy-marker takes a second argument TYPE
which specifies the insertion type of the new copied marker.

** When you create an overlay, you can specify the insertion type of
the beginning and of the end.  To do this, you can use two new
arguments to make-overlay: front-advance and rear-advance.

** The new function overlays-in returns a list of the overlays that
overlap a specified range of the buffer.  The returned list includes
empty overlays at the beginning of this range, as well as within the
range.

** The new function safe-length computes the length of a list.
It never gets an error--it treats any non-list like nil.
If given a circular list, it returns an upper bound for the number
of elements before the circularity.

** replace-match now takes a fifth argument, SUBEXP.  If SUBEXP is
non-nil, that says to replace just subexpression number SUBEXP of the
regexp that was matched, not the entire match.  For example, after
matching `foo \(ba*r\)' calling replace-match with 1 as SUBEXP means
to replace just the text that matched `\(ba*r\)'.

** The new keymap special-event-map defines bindings for certain
events that should be handled at a very low level--as soon as they
are read.  The read-event function processes these events itself,
and never returns them.

Events that are handled in this way do not echo, they are never
grouped into key sequences, and they never appear in the value of
last-command-event or (this-command-keys).  They do not discard a
numeric argument, they cannot be unread with unread-command-events,
they may not appear in a keyboard macro, and they are not recorded
in a keyboard macro while you are defining one.

These events do, however, appear in last-input-event immediately after
they are read, and this is the way for the event's definition to find
the actual event.

The events types iconify-frame, make-frame-visible and delete-frame
are normally handled in this way.

** encode-time now supports simple date arithmetic by means of
out-of-range values for its SEC, MINUTE, HOUR, DAY, and MONTH
arguments; for example, day 0 means the day preceding the given month.
Also, the ZONE argument can now be a TZ-style string.

** command-execute and call-interactively now accept an optional third
argument KEYS.  If specified and non-nil, this specifies the key
sequence containing the events that were used to invoke the command.

Re: September Gnus 0.13 is released

[Stefan Bodewig]

Hi,

I have two rather large problems with 0.13.

First and worst: I cannot post articles (neither `a' nor `f' nor `F'
works) because:

Signalling: (search-failed "^--text follows this line--$")
  re-search-forward("^--text follows this line--$")
  mail-position-on-field("Fcc")
  gnus-inews-insert-bfcc()
  gnus-new-news("hhu.test")
  gnus-post-news(post "hhu.test" nil "*Article*")
  gnus-group-post-news(nil)
* call-interactively(gnus-group-post-news)

The problem is gnus-inews-insert-bfcc calls
gnus-inews-narrow-to-headers and this excludes the
mail-header-separator. This way mail-position-on-field cannot find it
and that's all.

A quick hack to get my articles posted was to include
mail-header-separator into the header region by deleting the
match-beginnig part in gnus-inews-narrow-to-headers. Probably this
will totaly crash Gnus somewhere else.

My second problem: My mail has lost all the nice expireable-marks and
whatever I do they don't want to come back. Mark them with `E', leave
group, reenter and see: They are marked with an O. Don't know, if this
is nnbabyl specific.

Stefan

Re: September Gnus 0.13 is released

[Sudish Joseph]

Robert Nicholson writes:
> <larsi@ifi.uio.no> writes:
>> Anyways, Emacs 19.30 looks to be a really good Emacs release, so
>> everybody who has held off installing 19.29 will probably install
>> 19.30.  

> Anybody want to try and convince lars to keep 19.28 support in? Is
> the 19.30 stuff that good? What exactly does it allow you to do?

If it's a vote to keep 19.28 support in, I vote for yes.  :-)
But I doubt it's a vote...I guess I'll be staying at 0.12 for a long
time. :(

It'd be nice if someone pointed out what new feature of 19.29 it is
that ding is using, so that we may work around that and still upgrade.

-Sudish

Re: September Gnus 0.13 is released

[Robert Nicholson]

<larsi@ifi.uio.no> writes:

>"Paul J. Sanchez" <paul@whimsy.umsl.edu> writes:
>>Is there any way to restore emacs 19.28 support?  Some of us are
>>locked in...

>I'd suggest using Gnus 5.0.12, which supports lots of Emacsen.  Most
>of the new features in September Gnus are rather esoteric, I'd say.

With respect to 5.0.12.

I take it this is that one that FSF maintain now. Probably in their
own time. ie. not released separately to Emacs?

Has the Organisation bug I spoke about been fixed in .12?

>Anyways, Emacs 19.30 looks to be a really good Emacs release, so
>everybody who has held off installing 19.29 will probably install
>19.30.  

Anybody want to try and convince lars to keep 19.28 support in? Is
the 19.30 stuff that good? What exactly does it allow you to do?

-- 
             "Mary ate a little lamb and punk rock isn't dead"
            (PGP key: send email with Subject: request pgp key)

Re: September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

"Paul J. Sanchez" <paul@whimsy.umsl.edu> writes:

> Is there any way to restore emacs 19.28 support?  Some of us are
> locked in...

I'd suggest using Gnus 5.0.12, which supports lots of Emacsen.  Most
of the new features in September Gnus are rather esoteric, I'd say.

Anyways, Emacs 19.30 looks to be a really good Emacs release, so
everybody who has held off installing 19.29 will probably install
19.30.  

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: September Gnus 0.13 is released

[Paul J. Sanchez]

Lars,

Is there any way to restore emacs 19.28 support?  Some of us are
locked in...

Thanks.

---

--paul                             http://www.umsl.edu/~psanchez/
[L(aB)FFoDM # {WAL(1,t):t\in(0.5,1]}]

=================================================================
   The USA is so enormous, and so numerous are its schools,
   colleges and religious seminaries, many devoted to special
   religious beliefs ranging from the unorthodox to the dotty,
   that we can hardly wonder at its yielding a more bounteous
   harvest of gobbledygook than the rest of the world put
   together.
		-- Sir Peter Medawar
=================================================================

September Gnus 0.13 is released

[Lars Magne Ingebrigtsen]

Majorish changes since 0.12.  Be sure to do a thorough recompiling
("make") instead of doing a `byte-recompile' as many functions have
been made into macros (and vice versa).

You'll also get incorrect article counts in the group buffer before
entering/exiting the groups.  This will resolve itself after a while
-- you don't have to do anything in particular.

September Gnus now only works with Emacs 19.29 (and later), late Mules
and XEmacs 19.13. Emacs 19.28, in particular, is no longer
supported.

Oh, and in case you haven't heard -- Gnus 5.1 is included in the
pre-release Emacs 19.29.91.

Get it from <URL:http://www.ifi.uio.no/~larsi/sgnus.tar.gz> or 
"ftp.ifi.uio.no:/pub/emacs/gnus/".

ChangeLog since last release:

Wed Nov 15 06:13:48 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-score.el (gnus-score-get): Turned into a defsubst.
	(gnus-score-find-bnews): Slightly less funcalling.

	* gnus.el (gnus-group-real-name): Turned into a macro.
	(gnus-server-equal): Ditto.
	(gnus-server-add-address): Turned into defsubst.
	(gnus-server-get-method): Ditto.
	(gnus-secondary-method-p): Ditto.

Mon Nov 13 22:13:10 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-group-mode-map): Moved fetch-faq.

	* gnus-vis.el (gnus-button-alist): Be a bit more restrictive.

	* gnus-msg.el (gnus-inews-insert-headers): Would choke on empty
	headers.

	* nnml.el (nnml-make-nov-line): Include the Xref: in the nov line.

Mon Nov 13 21:54:36 1995    <morioka@jaist.ac.jp>

	* gnus.el (gnus-summary-save-in-rmail): Save original article
	buffer.

Mon Nov 13 15:10:28 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* nnsoup.el (nnsoup-open-server): Don't force using nnsoup as a
	posting agent.

	* gnus.el (gnus-info-group, gnus-info-level, gnus-info-read,
	gnus-info-method, gnus-info-options): New macros.  Massive changes
	throughout the file.
	(gnus-get-info): New macro.
	(gnus-group-add-score): New function.
	(gnus-summary-bubble-group): New function.
	(gnus-group-mode-map): New group sort submap.
	(gnus-group-sort-groups-by-alphabet,
	gnus-group-sort-groups-by-unread, gnus-group-sort-groups-by-level,
	gnus-group-sort-groups-by-score, gnus-group-sort-groups-by-rank,
	gnus-group-sort-groups-by-method): New commands and keystrokes.

	* nnsoup.el (nnsoup-set-variables): Autoload; doc fix.

	* gnus-score.el (gnus-score-headers): Score "header" names are now
	case-insensitive.

	* gnus.el (gnus-rebuild-thread): Didn't work when using a
	non-threaded display.

Sun Nov 12 00:11:34 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* nnmail.el (nnmail-use-long-file-names): New variable.
	(nnmail-group-pathname): Use it.

	* gnus.el (gnus-auto-select-first): Allow `best' as a value.

	* gnus-uu.el (gnus-uu-save-article): Quote lines that start with
	dashes. 

	* gnus-mh.el (gnus-mh-mail-setup): Don't use a (None) subject. 

	* gnus-msg.el (gnus-inews-insert-bfcc): New function.
	(gnus-new-news): Use it.

	* gnus.el (gnus-summary-generate-hook): New variable.
	(gnus-summary-prepare): Use it.

	* nnsoup.el (nnsoup-index-buffer): Disable undo.

	* gnus.el (gnus-select-newsgroup): Fetch old headers before
	scoring. 
	(gnus-dribble-read-file): Force setting the dribble buffer file
	name. 
	(gnus-summary-catchup-to-here): Treat `all' right, and catchup to
	the right article.
	(gnus-summary-catchup): Update mode line.
	(gnus-summary-refer-references): Didn't really work.
	(gnus-summary-toggle-header): Would barf if point weren't at
	point-min.

Sat Nov 11 11:21:58 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* nnmail.el (nnmail-move-inbox): Bind default directory before
	calling movemail.

	* nndoc.el (nndoc-type-to-regexp): Changed babyl body-begin regexp.

	* nnml.el (nnml-generate-nov-databases): Don't choke on files that
	start with empty lines.

	* gnus.el (gnus-souped-mark): New variable.
	(gnus-summary-mark-article-as-read): Use it.
	(gnus-set-mode-line): Would compute incorrect mode lines. 

	* gnus.el: Changes throughout making ticked and dormant articles
	subsets of the read articles instead of the unread articles. 

	* gnus-soup.el (gnus-soup-add-article): Use it.

	* gnus-msg.el (gnus-post-news): Respect to `to-group' group
	parameter. 

	* gnus.el (gnus-sublist-p): New function.
	(gnus-group-prepare-flat-list-dead): Faster implementation.

Fri Nov 10 03:17:03 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-newsgroup-threads): Double defvar.
	(gnus-newsgroup-prepared): New variable.
	(gnus-summary-setup-buffer): Use it.
	(gnus-summary-prepare-threads): Don't destroy threads while
	generating. 
	(gnus-remove-thread): Didn't remove gathered threads.
	(gnus-rebuild-thread): Didn't generate anything properly.
	(gnus-summary-refer-parent-article): Didn't find parent.

	* gnus-msg.el (gnus-mail-send-method): Removed variable.
	(gnus-auto-mail-to-author): Doc fix.

	* nnheader.el (nnheader-remove-header): Return the number of
	headers removed.

	* gnus.el (gnus-headers-de-quoted-unreadable): New function.
	(gnus-headers-decode-quoted-readable): New function.
	(gnus-article-de-quoted-unreadable): Use it.

Fri Nov 10 00:00:47 1995  Steven L. Baur <steve@miranova.com>

	* gnus-vis.el (gnus-header-button-alist): Recognize X-Url
	headers. 

Fri Nov 10 00:00:47 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-msg.el (gnus-delete-supersedes-headers): Also remove Xref
	and Lines.
	(gnus-summary-supersede-article): Delete multi-line headers.
	(gnus-news-followup): Insert a few empty lines in new articles.
	(gnus-mail-reply): Put point the right place when replying.
	(gnus-inews-organization): Don't interpret signatures that begin
	with ~ as strings.
	(gnus-news-followup): Respect the Newsgroup header.

	* nnsoup.el (nnsoup-write-buffers): New function.
	(nnsoup-request-close): Use it.
	(nnsoup-pack-replies): Ditto.

	* gnus-soup.el (gnus-soup-parse-replies): Didn't kill buffer.
	(gnus-soup-write-prefixes): Would change current buffer.

Thu Nov  9 20:54:35 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-mouse-face-function): More efficient implementation.
	(gnus-max-width-function): Ditto.

	* gnus-msg.el (gnus-inews-news): Get the error message from the
	right backend.

	* gnus.el (gnus-summary-limit-to-score): Don't infloop.
	(gnus-request-post-buffer): Removed function.
	(gnus-method-option-p): New function.
	(gnus-post-method): New function.
	(gnus-request-post): Use it.

	* nnsoup.el (nnsoup-write-active-file): Would possibly kill the
	active file.

Mon Nov  6 13:16:33 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-msg.el (gnus-new-news): Removed prompting for group name.
	(gnus-group-post-news): Prompt for group name.
	(gnus-inews-do-fcc): Rewrite.

	* gnus.el (gnus-group-get-parameter): New function.

Sat Nov  4 19:24:57 1995  sudish joseph  <joseph@cis.ohio-state.edu>

	* gnus-msg.el (gnus-group-post-news): Use the group under point as
	  the default when composing the post buffer.  (This means that
	  `a' over a mail group will get you a *mail* buffer.)  Using a
	  prefix ARG will force a fresh post buffer (i.e., no default
	  group is used).

Mon Nov  6 12:54:40 1995  steve@miranova.com (Steven L. Baur)

	* gnus-topic.el (gnus-topic-toggle-topic): New command and
	keystroke. 

Sat Nov  4 19:07:31 1995  Per Abrahamsen  <abraham@dina.kvl.dk>

	* gnus-vis.el (gnus-group-make-menu-bar): Add key description for
	the "See old articles" entry and made it run
	gnus-group-select-group with an argument. 
	* gnus.el (gnus-group-select-group-all): Deleted.

Mon Nov  6 12:22:20 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-save-newsrc-file): Set local `version-control' to
	`never'. 
	(gnus-gnus-to-newsrc-format): Ditto.

	* gnus-msg.el (gnus-new-news): Move point to the right place.
	(gnus-sendmail-mail-setup): Ditto.

Sun Nov  5 10:05:47 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-msg.el (gnus-configure-posting-styles): Make sure that
	`gnus-newsgroup-name' is set.

	* gnus-topic.el (gnus-group-add-to-topic): Remove process marks. 

	* nnml.el (nnml-request-move-article): The article has to be
	deletable to be moved.
	* nnmh.el (nnmh-request-move-article): Ditto.

	* nnmh.el (nnmh-deletable-article-p): New function.

	* nnml.el (nnml-deletable-article-p): New function.

	* gnus.el (gnus-data-compute-positions): Doc fix.
	(gnus-summary-sort): Make sure positions were updated.
	(gnus-request-article-this-buffer): Set original article buffer to
	be read-only.

Fri Nov  3 03:01:09 1995  Lars Magne Ingebrigtsen  <larsi@narfi.ifi.uio.no>

	* gnus.el (gnus-request-article-this-buffer): Make sure all
	overlays are dead.

Fri Nov  3 00:41:22 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-xmas.el: Removed mouse tracker.

	* gnus.el (gnus-mouse-face-function): Redefined so that it also
	works under XEmacs.

Thu Nov  2 03:40:22 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-batch-score): Don't generate threads and stuff.
	(gnus-sort-threads): Better message.

Tue Oct 31 21:26:35 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus-topic.el (gnus-topic-remove-topic): Would eat groups under
	emtpy topics.

	* gnus.el (gnus-simplify-buffer-fuzzy): Would strip trailing
	newlines. 
	(gnus-group-list-groups): Update format specs.
	(gnus-summary-limit-children): Didn't mark as read.

Mon Oct 30 00:09:42 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-summary-find-matching): Wouldn't do `backward' ok.
	(gnus-summary-limit-to-subject): Don't just limit to articles
	after point.
	(gnus-articles-to-read): Respond properly to numerical prefixes.

	* gnus-msg.el (gnus-inews-article): Do the To/X-To shuffle dance.

	* gnus.el (gnus-summary-expire-articles): Be less complaining when
	doing total-expiry.

	* gnus-msg.el (gnus-mail-send): Remove empty headers before
	sending. 
	(gnus-inews-remove-empty-headers): New function.

	* gnus.el (gnus-summary-find-next): Respect
	`gnus-summary-check-current'. 
	(gnus-summary-find-prev): Ditto.
	(gnus-summary-mode-map): Limit map had disappeared.
	(gnus-summary-limit-children): Wouldn't limit properly with
	gnus-fetch-old-headers 'some.

Sun Oct 29 23:37:17 1995  Lars Ingebrigtsen  <lars@eyesore.no>

	* nnmh.el: Use nnmail's new definition.
	* nnml.el: Ditto.

	* nnmail.el (nnmail-group-pathname): Use nnmh's definition.

	* gnus.el (gnus-group-startup-message): Change.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen