Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: September Gnus 0.56 is released
Date: Sat, 23 Mar 1996 01:48:12 +0100	[thread overview]
Message-ID: <w8ska0cski2.fsf@ylfing.ifi.uio.no> (raw)

Bug fixes.

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:

Sat Mar 23 00:01:56 1996  Lars Magne Ingebrigtsen  <larsi@aegir.ifi.uio.no>

	* gnus.el (gnus-group-add-score): Would bug out on dead groups.

Fri Mar 22 22:30:32 1996  Lars Magne Ingebrigtsen  <larsi@aegir.ifi.uio.no>

	* gnus.el (gnus-get-newsgroup-headers): Would ignore In-Reply-To
	headers. 

	* gnus-uu.el (gnus-uu-uustrip-article): Handle multiple uuencoded
	files in each article.

	* gnus-msg.el (gnus-inews-article): Switch to buffer where
	`gnus-inews-article-hook' is run to make ispelling possible.

	* gnus.el (gnus-summary-last-article-p): New function.
	(gnus-summary-next-page): Wouldn't go past last article in
	narrowed buffers.
	(gnus-group-make-help-group): Would create under false name.

Fri Mar 22 22:23:20 1996  Greg Stark  <gsstark@mit.edu>

	* nneething.el (nneething-make-head): Create better heads.

Fri Mar 22 18:58:17 1996  Lars Magne Ingebrigtsen  <lars@eyesore.no>

	* gnus-score.el (gnus-score-body): Would bug out.

	* nnfolder.el (nnfolder-retrieve-headers): Make sure the buffer
	exists before setting it. 

	* gnus.el (gnus-summary-exit): Don't run prepare-exit-hook when
	exiting temporarliy.

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


                 reply	other threads:[~1996-03-23  0:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=w8ska0cski2.fsf@ylfing.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).