Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: September Gnus 0.40 is released
Date: Wed, 21 Feb 1996 03:26:33 +0100	[thread overview]
Message-ID: <w8s68d1ct34.fsf@eistla.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:

Wed Feb 21 00:21:56 1996  Lars Magne Ingebrigtsen  <larsi@ifi.uio.no>

	* gnus.el (gnus-summary-refer-parent-article): Also check the NOV
	references. 

	* gnus-salt.el (gnus-possibly-generate-tree): Don't generate trees
	for pseudo-articles.

	* nnvirtual.el (nnvirtual-retrieve-headers): Make sure the group
	exists. 

	* gnus.el (gnus-summary-read-group): Search all frames when
	recentering the group buffer.
	(gnus-summary-hide-thread): Didn't hide dummy threads.

	* gnus.el (gnus-summary-prepare-threads): Dummy roots would
	swallow the following article.

	* gnus-msg.el (gnus-new-empty-mail): New function.
	(gnus-summary-resend-bounced-mail): Use it.

	* gnus-picon.el (gnus-picons-display-x-face): Make sure buffer
	exists. 

Tue Feb 20 04:45:34 1996  Lars Ingebrigtsen  <lars@eyesore.no>

	* gnus.el (gnus-group-set-current-level): Error if not a group on
	the current line.
	(gnus-summary-next-page): Don't go to the next article when 'never
	and at the end of the group.
	(gnus-group-make-group): Make sure the server is opened.
	(gnus-read-descriptions-file): Make sure the method is a method
	and not a server.

	* gnus-msg.el (gnus-copy-article-buffer): Ditto.
	(gnus-forward-insert-buffer): Ditto.

	* gnus-cite.el (gnus-cite-parse): Use `gnus-set-text-properties'.

	* nnheader.el (nnheader-temp-write): Would bug out on nil files. 

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


             reply	other threads:[~1996-02-21  2:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-21  2:26 Lars Magne Ingebrigtsen [this message]
1996-02-21  3:20 ` Steven L Baur
1996-02-21 11:06   ` Per Abrahamsen
1996-02-21 19:00     ` Steven L Baur
1996-02-21 21:50       ` Andy Eskilsson
1996-02-22  1:12       ` Lars Magne Ingebrigtsen
1996-02-22  8:22         ` d. hall
1996-02-22 18:03           ` Lars Magne Ingebrigtsen
1996-02-22 20:49             ` Steven L Baur
1996-02-21  4:14 ` d. hall
1996-02-21  6:55   ` Gnus Memory usage Steven L Baur
1996-02-21 16:38     ` Wes Hardaker
1996-02-22  1:12       ` Lars Magne Ingebrigtsen
1996-02-22 23:19         ` Wes Hardaker
1996-02-22 23:50           ` Lars Magne Ingebrigtsen
1996-02-23 17:19             ` Wes Hardaker
1996-02-24  7:44               ` Lars Magne Ingebrigtsen
1996-02-24  9:26                 ` d. hall
1996-02-26 18:01                   ` Stephen Peters
1996-02-26 18:12                 ` Wes Hardaker
1996-02-23  1:39           ` Steven L Baur
1996-02-23 17:24             ` Wes Hardaker
1996-02-23 21:57             ` Mark Denovich
1996-02-24  7:44               ` Lars Magne Ingebrigtsen
1996-02-24 22:08                 ` dynamic ip (Re: Gnus Memory usage) Felix Lee
1996-02-24 22:33                   ` Lars Magne Ingebrigtsen
1996-02-25  0:35                     ` Felix Lee
1996-02-21 17:59     ` Gnus Memory usage Mark Borges

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=w8s68d1ct34.fsf@eistla.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).