From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: September Gnus 0.24 is released
Date: Sun, 17 Dec 95 18:02:03 +0100 [thread overview]
Message-ID: <w8sd99neiap.fsf@narfi.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:
Sun Dec 17 16:06:11 1995 Lars Magne Ingebrigtsen <larsi@hymir.ifi.uio.no>
* nndoc.el (nndoc-guess-digest-type): Didn't grok MIME digests.
* gnus.el (gnus-all-windows-visible-p): Would bug out on buffers
that didn't exist.
(gnus-all-windows-visible-p): Allow strings in buffer-config.
(gnus-configure-frame): Ditto.
(gnus-remove-text-with-property): Didn't remove all text.
* gnus-uu.el (gnus-uu-grab-articles): Would delete files after
decoding them.
Sun Dec 17 00:12:34 1995 Lars Ingebrigtsen <lars@eyesore.no>
* gnus-score.el (gnus-score-followup-article): New command.
(gnus-score-followup-thread): New command.
* gnus.el (gnus-compile): New implementation; save in
.newsrc.eld.
(gnus-summary-rethread-thread): New command and keystroke.
Sat Dec 16 22:22:58 1995 Lars Ingebrigtsen <lars@eyesore.no>
* nnspool.el (nnspool-find-article-by-message-id): Decompose the
output; renamed.
(nnspool-request-article): Use the function.
(nnspool-retrieve-headers): Ditto.
* gnus.el (gnus-group-catchup): Do the auto-expirable thaang.
* gnus-cache.el (gnus-cache-possibly-enter-article): Don't enter
empty articles into the cache.
* nnspool.el (nnspool-find-nov-line): Would often not find the
right line.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next reply other threads:[~1995-12-17 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-17 17:02 Lars Magne Ingebrigtsen [this message]
[not found] <7mzum5h3@totally-fudged-out-message-id>
1995-12-19 17:27 ` Manoj Srivastava
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=w8sd99neiap.fsf@narfi.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).