From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Gnus v5.2.30 is released
Date: 29 Jun 1996 01:03:40 +0200 [thread overview]
Message-ID: <w8sohm3pm4p.fsf@ylfing.ifi.uio.no> (raw)
Bug fixes + earcon.
Get it from <URL:http://www.ifi.uio.no/~larsi/gnus.tar.gz> or
"ftp.ifi.uio.no:/pub/emacs/gnus/".
ChangeLog since last release:
Sat Jun 29 01:03:19 1996 Lars Magne Ingebrigtsen <larsi@ylfing.ifi.uio.no>
* gnus.el: Gnus v5.2.30 is released.
Sat Jun 29 00:23:44 1996 Lars Magne Ingebrigtsen <larsi@ylfing.ifi.uio.no>
* gnus.el (gnus-article-read-summary-keys): Deal with message
composition more gracefully.
Fri Jun 28 23:58:37 1996 Lars Magne Ingebrigtsen <larsi@ylfing.ifi.uio.no>
* gnus.el (gnus-group-describe-group): Re-read when given a
prefix.
Fri Jun 28 23:34:17 1996 Lars Magne Ingebrigtsen <larsi@aegir.ifi.uio.no>
* gnus.el (gnus-group-kill-level): Put groups on killed list.
* nnfolder.el (nnfolder-read-folder): Would bug out when group not
in active file.
Fri Jun 28 22:42:49 1996 Lars Magne Ingebrigtsen <larsi@ylfing.ifi.uio.no>
* gnus-score.el (gnus-summary-score-entry): Get rid of text
props.
* gnus.el (gnus-article-read-summary-keys): Allow `A RET' to work
properly.
(gnus-summary-limit): Inhibit marking low-scored articles as
read.
* gnus-msg.el (gnus-article-mail): Reply from the right address.
(gnus-article-mail): Yank properly.
* gnus.el (gnus-article-mode-map): Entry for info find node.
(gnus-summary-describe-briefly): Display proper message.
* smiley.el (smiley-circle-color): Doc fix.
* gnus.el (gnus-summary-prepare-threads): Would display expunged
articles after a dummy line.
(gnus-group-faq-directory): Doc fix.
(gnus-summary-mode): Clear moved inboxes.
Fri Jun 28 21:48:27 1996 Steven L. Baur <steve@miranova.com>
* earcon.el: New file.
* gnus-sound.el: New file.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
reply other threads:[~1996-06-28 23:03 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=w8sohm3pm4p.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).