From: Mark Triggs <mst@dishevelled.net>
Cc: "Kevin Greiner" <kgreiner@xpediantsolutions.com>,
kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: HEADS UP: Largely rewritten gnus-agent implementation.
Date: Mon, 25 Nov 2002 00:02:08 +1100 [thread overview]
Message-ID: <877kf3f7e7.fsf@dishevelled.net> (raw)
In-Reply-To: <84bs4ggtnq.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Sat, 23 Nov 2002 17:03:37 +0100")
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)
gnus-range-difference(((1471 . 2560)) (1471 1472 1473 1474 1475 1476
1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490
1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518
1519 1520 ...))
gnus-summary-insert-old-articles(nil)
call-interactively(gnus-summary-insert-old-articles)
recursive-edit()
[snip byte-code]
debug(error (void-function gnus-range-difference))
gnus-range-difference(((1471 . 2560)) (1471 1472 1473 1474 1475 1476
1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490
1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518
1519 1520 ...))
gnus-summary-insert-old-articles(nil)
call-interactively(gnus-summary-insert-old-articles)
A grep of the source didn't turn up a defun for 'gnus-range-difference'
anywhere, but I do have a 'gnus-list-range-difference' (in
gnus-range.el).
Also, I'm entering the server buffer and agentizing my nntp server using
'J a', but I'm finding that when I save ~/.newsrc.eld and restart gnus,
the server is no longer agentized. I don't actually use the agent for
fetching articles, but I do use it for caching article headers. Can
anyone else reproduce this?
Thanks again. All the best,
Mark
--
Mark Triggs
<mst@dishevelled.net>
next prev parent reply other threads:[~2002-11-24 13:02 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 [this message]
2002-11-24 14:08 ` Kai Großjohann
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=877kf3f7e7.fsf@dishevelled.net \
--to=mst@dishevelled.net \
--cc=kai.grossjohann@uni-duisburg.de \
--cc=kgreiner@xpediantsolutions.com \
/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).