From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: virtual nnvirtual
Date: Wed, 23 Mar 2022 22:51:25 +0800 [thread overview]
Message-ID: <87ee2shgcy.fsf@ust.hk> (raw)
In-Reply-To: <87a6dgst4w.fsf@ucl.ac.uk>
>>>>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
[...]
ESF> For A T,
>> This should work (provided searching is configured for the
>> constituent groups).
ESF> it doesn't work but I don't think it's the searching element,
ESF> or maybe it is. I get an error with the following [elided]
ESF> backtrace:
No, probably not the searching element.
[...]
ESF> gnus-summary-limit((143 154 165 174 176 189 192 190 191 193 231
ESF> 232 233 253 255 250 259 262 245 241 240 218 227 205 213 204 248
ESF> 197 185 178 221 224 177 168 169 163 194 196 198 199 201 202 143
ESF> 154 165 174 176 189 192 190 ...))
This is definitely not right. This should be a unique list of article
numbers and I can see repeats. Also it should be sorted.
And I think I see the problem---I'm trying to not store the artlist,
which can be very long, and just regenerate it when needed. But the
thread retrieval /adds/ the new articles to the artlist, and this causes
things to get messed up when it tries to generate the new list. I can
fix this, but I need to think about the best way.
Thanks for testing!
Best,
Andy
--
Andrew Cohen
next prev parent reply other threads:[~2022-03-23 14:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 0:45 Andrew Cohen
2022-03-23 8:14 ` Eric S Fraga
2022-03-23 11:53 ` Eric S Fraga
2022-03-23 12:02 ` Eric S Fraga
2022-03-23 12:53 ` Andrew Cohen
2022-03-23 13:19 ` Eric S Fraga
2022-03-23 14:51 ` Andrew Cohen [this message]
2022-03-23 15:28 ` Eric S Fraga
2022-03-23 15:00 ` Eric Abrahamsen
2022-03-23 15:31 ` Eric S Fraga
2022-03-24 5:30 ` Andrew Cohen
2022-03-24 7:27 ` Eric S Fraga
2022-03-23 15:33 ` Eric S Fraga
2022-03-25 0:39 ` Andrew Cohen
2022-03-25 4:53 ` Andrew Cohen
2022-03-25 9:15 ` Eric S Fraga
2022-03-25 9:27 ` Andrew Cohen
2022-03-25 9:35 ` Eric S Fraga
2022-03-25 9:39 ` Andrew Cohen
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=87ee2shgcy.fsf@ust.hk \
--to=acohen@ust.hk \
--cc=ding@gnus.org \
/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).