From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: HEADS UP: Largely rewritten gnus-agent implementation.
Date: Sun, 24 Nov 2002 15:08:18 +0100 [thread overview]
Message-ID: <848yzj2h7x.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <877kf3f7e7.fsf@dishevelled.net>
Mark Triggs <mst@dishevelled.net> writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> I think that's it! Please report your findings.
>
> I've just checked out the latest source from CVS, and can certainly see
> the improvement (thanks Kevin :o), but have had a few slight hiccups..
>
> Doing '/ o' in the summary buffer (gnus-summary-insert-old-articles) I
> get the following error:
>
>
> Debugger entered--Lisp error: (void-function gnus-range-difference)
Ick.
I will check in the following fix in a jiffy. Does it work?
cvs server: Diffing .
cvs server: Diffing contrib
cvs server: Diffing etc
cvs server: Diffing etc/gnus
cvs server: Diffing etc/smilies
cvs server: Diffing lisp
Index: lisp/ChangeLog
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/ChangeLog,v
retrieving revision 6.1682
diff -u -r6.1682 ChangeLog
--- lisp/ChangeLog 2002/11/23 15:56:57 6.1682
+++ lisp/ChangeLog 2002/11/24 14:10:28
@@ -1,3 +1,9 @@
+2002-11-24 Kai Gro,A_(Bjohann <kai.grossjohann@uni-duisburg.de>
+
+ * gnus-sum.el (gnus-summary-insert-old-articles): Use
+ gnus-remove-from-range instead of gnus-range-difference which
+ doesn't exist.
+
2002-11-23 Kai Gro,A_(Bjohann <kai.grossjohann@uni-duisburg.de>
From Kevin Greiner <kgreiner@xpediantsolutions.com>.
Index: lisp/gnus-sum.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-sum.el,v
retrieving revision 6.239
diff -u -r6.239 gnus-sum.el
--- lisp/gnus-sum.el 2002/11/23 15:56:57 6.239
+++ lisp/gnus-sum.el 2002/11/24 14:10:50
@@ -11178,7 +11178,7 @@
;;; (gnus-sorted-difference
;;; (gnus-uncompress-range (list gnus-newsgroup-active))
;;; old)
- (gnus-range-difference (list gnus-newsgroup-active) old)
+ (gnus-remove-from-range (list gnus-newsgroup-active) old)
)
(setq len (gnus-range-length older))
(cond
cvs server: Diffing texi
cvs server: Diffing texi/etc
cvs server: Diffing texi/herds
cvs server: Diffing texi/misc
cvs server: Diffing texi/picons
cvs server: Diffing texi/ps
cvs server: Diffing texi/screen
cvs server: Diffing texi/smilies
cvs server: Diffing texi/xface
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-11-24 14:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 16:03 Kai Großjohann
2002-11-23 18:40 ` Danny Siu
2002-11-23 20:27 ` Kai Großjohann
2002-11-23 20:32 ` Kai Großjohann
2002-11-23 18:45 ` Danny Siu
2002-11-23 20:29 ` Kai Großjohann
2002-11-24 15:32 ` Danny Siu
2002-11-24 16:02 ` Danny Siu
2002-11-25 3:07 ` Henrik Enberg
2002-11-25 16:55 ` Henrik Enberg
2002-11-25 20:26 ` Kai Großjohann
2002-11-26 2:29 ` Kevin Greiner
2002-11-26 7:28 ` Kai Großjohann
2002-11-24 8:43 ` Denis Yakovlev
2002-11-26 3:09 ` Kevin Greiner
2002-11-24 13:02 ` Mark Triggs
2002-11-24 14:08 ` Kai Großjohann [this message]
2002-11-24 14:27 ` Mark Triggs
2002-11-25 7:28 ` Kai Großjohann
2002-11-25 14:42 ` Mark Triggs
2002-11-25 14:48 ` Kai Großjohann
2002-11-25 16:41 ` Kevin Greiner
2002-11-25 20:23 ` Kai Großjohann
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=848yzj2h7x.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).