Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: virtual nnvirtual
Date: Wed, 23 Mar 2022 13:19:59 +0000	[thread overview]
Message-ID: <87a6dgst4w.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87mthghlu9.fsf@ust.hk>

Hi Andrew,

thank you for the long response to my queries.  Very helpful.

Regarding /o, now it makes sense (the cycling nature of the retrieval)
and, yes, it seems to be working just fine.  Because some of the groups
in the virtual collection have not had any recent activity, I was
confused by seeing significantly old articles in the list provided.  I
now know that I need to multiply the number of messages, M, to retrieve
by N, where N is the number of groups in the virtual collection, to
ensure I get the M most recent emails I'm looking for.  Simple enough,
especially if I then sort by date.  Thank you for explaining this!

For A T,

> This should work (provided searching is configured for the constituent
> groups).

it doesn't work but I don't think it's the searching element, or maybe
it is.  I get an error with the following [elided] backtrace:

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  #f(compiled-function () #<bytecode -0x5da3a498744c248>)()
  gnus-summary-highlight-line()
  gnus-summary-prepare-threads((... ... ... ... ... ... ... ... ... ... ... ... ... ... ...))
  gnus-summary-prepare()
  gnus-summary-limit((143 154 165 174 176 189 192 190 191 193 231 232 233 253 255 250 259 262 245 241 240 218 227 205 213 204 248 197 185 178 221 224 177 168 169 163 194 196 198 199 201 202 143 154 165 174 176 189 192 190 ...))
  gnus-summary-limit-include-thread("..." nil)
  gnus-summary-refer-thread()
  nnselect-request-thread([4887 "..." ...])
  gnus-request-thread(...)
  gnus-summary-refer-thread(nil)
  funcall-interactively(gnus-summary-refer-thread nil)
  command-execute(gnus-summary-refer-thread)

The thread I want is there but there are also many other articles.  The
particular thread has 4 articles in it.  If I ask for the thread
starting in the right group, I get those articles that are in the thread
in that group.

Any suggestions?  I can try without compiled code to see, if you wish?

And, yes, using nnselect, i.e. a more up to date code base for this
functionality, is bound to be helpful.

Thank you,
eric

-- 
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2



  reply	other threads:[~2022-03-23 13:20 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 [this message]
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
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=87a6dgst4w.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).