From: Andrew Cohen <acohen@ust.hk>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: virtual nnvirtual
Date: Thu, 24 Mar 2022 13:30:47 +0800 [thread overview]
Message-ID: <874k3ngbnc.fsf@ust.hk> (raw)
In-Reply-To: <87a6dgst4w.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 23 Mar 2022 13:19:59 +0000")
>>>>> "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:
[...]
ESF> The thread I want is there but there are also many other
ESF> articles. The particular thread has 4 articles in it. If I
ESF> ask for the thread starting in the right group, I get those
ESF> articles that are in the thread in that group.
ESF> Any suggestions? I can try without compiled code to see, if
ESF> you wish?
I thought I had an idea what was wrong but turns out not so much. I have
tried and failed to reproduce this error (I am only trying imap since
that is what I have installed).
Maybe we can narrow it down to a simpler test case (debugging is quite
painful if you have lots of articles). First, maybe try a single
component group (create a new nnvirtual group with the convenience
function and in answer to the component group prompt use a list that
contains a single group; choose a group that has the article you want to
do thread referral on).
Does this work? If so, try adding a second group and see if it still
works. If not, we have a simpler test case to work on.
Once we have a simple enough test case I can walk you through debugging
the thread referral function to see whats what.
Best,
Andy
--
Andrew Cohen
next prev parent reply other threads:[~2022-03-24 5:31 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
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 [this message]
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=874k3ngbnc.fsf@ust.hk \
--to=acohen@ust.hk \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).